On Wed, Nov 14, 2018 at 10:58 AM Tom Ritter wrote:
> On Wed, Nov 14, 2018 at 3:17 PM Ehsan Akhgari
> wrote:
> > What are your plans with regards to implementing the second part? Can
> > these reports be sent cross-origin? (From the spec, it seems like the
> > answer is yes.) If so, how are yo
On 11/13/18 10:33 AM, Andrea Marchesini wrote:
*Summary*: Reporting API allows the page to receive notifications such as
the usage of deprecated APIs and FeaturePolicy violations.
I decided to implement this API, because it is required in the
web-platform-tests for FeaturePolicy.
Reporting API c
Scroll anchoring should benefit both desktop and mobile content.
I have a feeling the biggest impact will be on mobile though. Scroll anchoring
should help there when the viewport resizes from a rotation, not just as content
loads.
There's a good video in the Chrome announcement here [1].
I've a
This is great news! In a recent study of Fennec's perceived performance,
users ranked 16 criteria for evaluating mobile browser responsiveness.
#1 was "Not having the page jump around when scrolling". For a point of
reference for just how important that is, "Loading a website" was only
#3. :)
Apologies. The target release is 66, while Chrome released this feature in M56.
‐‐‐ Original Message ‐‐‐
On Wednesday, November 14, 2018 3:05 PM, Ryan Hunt wrote:
> Summary:
>
> Scroll anchoring aims to prevent user experience disruptions from content
> loading outside the viewport an
Summary:
Scroll anchoring aims to prevent user experience disruptions from content
loading outside the viewport and causing the page to jump around.
Bug: Bug 1305957
Link to standard:
https://drafts.csswg.org/css-scroll-anchoring/
Platform coverage: All platforms
Estimated or target release:
> Is it needed for any other reason? If not, this seems like a bug in the
> tests: they should not be coupling the two specs together.
>
Well, in this way, these 2 APIs can test each other: we could use
deprecated APIs to check ReportingObserver notifications, but there is not
a common set of dep
On 11/13/18 4:33 AM, Andrea Marchesini wrote:
I decided to implement this API, because it is required in the
web-platform-tests for FeaturePolicy.
Is it needed for any other reason? If not, this seems like a bug in the
tests: they should not be coupling the two specs together.
-Boris
__
On Wed, Nov 14, 2018 at 3:17 PM Ehsan Akhgari wrote:
> What are your plans with regards to implementing the second part? Can
> these reports be sent cross-origin? (From the spec, it seems like the
> answer is yes.) If so, how are you planning to handle issues such as
> sending these reports to
Finally something what solving problem of missing "word-break: break-word"
(https://jsfiddle.net/ofgd83um/80/)
When it will be shipped to stable?
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
On Tue, Nov 13, 2018 at 4:33 AM Andrea Marchesini
wrote:
> Reporting API covers 2 different features:
> a. reporting to the current page, via ReportingObserver
> b. reporting to a remote server, known via 'report-to' HTTP header.
> My implementation covers only the first aspect. However I also ha
Finally something can slove problem of missing "word-break: break-word"
https://jsfiddle.net/ofgd83um/80/
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
12 matches
Mail list logo
