Intent to ship: Visual Viewport API on Android

2019-05-08 Thread Botond Ballo
Hi everyone!

I would like to ship the Visual Viewport API [1] on Android. The
initial implementation [2] was done in Firefox 63 behind the pref
"dom.visualviewport.enabled" (see "Intent to Implement" thread [3]).
It has since seen bug fixes, polish, and expanded test coverage.

I intend to ship it on Android only for now. The API is primarily
useful in scenarios involving pinch-zooming, and we don't currently
support pinch-zooming on desktop. I intend to enable it on desktop
concurrently with support for pinch-zooming at a later date.

Target release: Firefox 68 or 69, depending on when the patches are
ready. If it doesn't make 68, I would like to get it into Fennec
68.1esr, as it's an important web compat feature.

Tracking bug for shipping: https://bugzilla.mozilla.org/show_bug.cgi?id=1512813

Status in other implementation:
  Blink: Shipping since Chrome 61 [4]
  Safari: Available in Preview version [5]

Web platform tests: The feature has good WPT coverage, with a mix of
automatic and manual tests. We are now [6] passing almost all tests on
Android; of the two remaining failures, one is a test harness
limitation [7], and the other is pending resolution of a spec issue
[8]. There are also a couple of tests which are not applicable to
Android because they involve reflowing zoom which Android does not
support.

Any thoughts / feedback is appreciated!

Thanks,
Botond

[1] https://github.com/WICG/visual-viewport/
[2] https://bugzilla.mozilla.org/show_bug.cgi?id=1357785
[3] 
https://groups.google.com/d/topic/mozilla.dev.platform/gchNtWfv_bk/discussion
[4] https://www.chromestatus.com/feature/5737866978131968
[5] https://webkit.org/status/#feature-visual-viewport-api
[6] https://bugzilla.mozilla.org/show_bug.cgi?id=1477610
[7] https://bugzilla.mozilla.org/show_bug.cgi?id=1547827
[8] https://bugzilla.mozilla.org/show_bug.cgi?id=1543485
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Intent to Implement and Ship: CSSStyleSheet.rules, CSSStyleSheet.removeRule, CSSStyleSheet.addRule

2019-05-08 Thread Emilio Cobos Álvarez
Summary: Implement and spec some non-standard CSSOM APIs to converge 
with every other browser, since they're unlikely to ever remove their 
implementations and the lack of them causes compat issues for us, see 
the bug, the CSSWG issue [1] and everything cross-linked from there.


Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1545823

Link to standard: https://github.com/w3c/csswg-drafts/pull/3900

Platform coverage: All

Estimated or target release: 68

Preference behind which this will be implemented: None

Is this feature enabled by default in sandboxed iframes? Yes

DevTools bug: N/A

Do other browser engines implement this? Yes, all of them, since 
basically forever (see https://github.com/whatwg/compat/issues/98).


Only know difference is that Blink and my implementation returns a live 
object for CSSStyleSheet.rules, while WebKit returns a static list of 
rules. I've filed a bug on WebKit to consider simplifying their code and 
making this just an alias to converge: https://webkit.org/b/197725.


web-platform-tests: Added as part of the implementation.

Is this feature restricted to secure contexts? No, it's a legacy API, 
mostly aliases of already-non-restricted APIs.


As always, let me know if you think there's any concerns with proceeding.

 -- Emilio

[1]: https://github.com/w3c/csswg-drafts/issues/3814
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Changes to autoland repository configuration

2019-05-08 Thread Kim Moir
If you don’t pull from the autoland repository, you can stop reading.

The autoland repository has a “special” configuration: Until its changesets
are merged into mozilla-central, they are in the mercurial ‘draft’
phase[1][2].  On Thursday May 9, 2019 we will change the repository to be
configured like mozilla-inbound. After this change is implemented all
changesets landed by Lando to autoland will be in the public state. Also,
running `hg wip` after pulling autoland locally will no longer cause issues.

If you have questions about this change, please reach out in the #lando
slack channel. If you find an issue related to this change, file a
regressed by bug against
https://bugzilla.mozilla.org/show_bug.cgi?id=1538695

[1] https://hg.mozilla.org/integration/autoland/

[2] https://www.mercurial-scm.org/wiki/Phases


Kim
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform