Thanks Emilio!
Here are the bugs filed to summarize our test behavior that diverges
from Blink's.
[1] Dependencies on other less mature specifications.
* Bug 1867737
<https://bugzilla.mozilla.org/show_bug.cgi?id=1867737> - Popover wpt
test failures due to lack of Anchor positioning support
* Bug 1867743
<https://bugzilla.mozilla.org/show_bug.cgi?id=1867743> - support
popover=hint. Not in spec and still in
discussion(https://github.com/whatwg/html/pull/9778)
* Bug 1867754
<https://bugzilla.mozilla.org/show_bug.cgi?id=1867754> - Support
popover hover triggering on buttons. Not in spec. It is mentioned here
<https://bugs.chromium.org/p/chromium/issues/detail?id=1416284> that
this capability is gated behind the HTMLPopoverHint feature.
[2][3][4]:
* Bug 1867755
<https://bugzilla.mozilla.org/show_bug.cgi?id=1867755> -
popover-overlay.html fails due to lack of overlay support
Others:
* There are also a couple of flat tree related tests that fail for
all platforms. This is due to test_driver actions don't work on targets
in shadow DOM. The bug is filed at Bug 1867756
<https://bugzilla.mozilla.org/show_bug.cgi?id=1867756>.
* In the wpt.fyi link in your email, popover-events.html fails for
Firefox. This is fixed at D195091
<https://phabricator.services.mozilla.com/D195091> and hope to reflect
on the result soon.
I think this has covered all the test failures we have at wpt.fyi for
the moment. Do please let me know if you need any further information.
Many thanks,
Ziran
On 11/29/23 16:31, Emilio Cobos Álvarez wrote:
Hi Ziran,
Thanks for your work on this! Generally looks in pretty good shape.
I have a question about the tests. There are some existing tests here
<https://wpt.fyi/results/html/semantics/popovers> where our behavior
(and WebKit's) diverges from Blink's. I don't think they block
shipping necessarily since Safari is also shipping, but it'd be good
to know if they are:
1. Dependencies on other less mature specifications (like anchor
positioning, popover=hint etc). It seems there are a couple like that.
2. Issues with the test harness.
3. Actual bugs (maybe low priority ones).
4. Something else?
Would there be any chance of having a quick summary of those? At least
for (2), (3) and (4) it'd be good to have bugs on file.
Assuming nothing problematic arises from that analysis, turning on by
default and letting it ride the trains sounds good to me.
Thanks again!
-- Emilio
On Wed, Nov 29, 2023 at 3:45 PM Ziran Sun <[email protected]> wrote:
Correcting the link -
/Bug to turn on by default/:
https://bugzilla.mozilla.org/show_bug.cgi?id=1866993
Ziran
On 11/29/23 14:18, Ziran Sun wrote:
Hi all,
As of Firefox 122, I intend to turn the Popover attribute on by
default.
It has been developed behind the dom.element.popover.enabled
preference at https://bugzilla.mozilla.org/show_bug.cgi?id=1808823.
Status in other browsers is:
Chrome - supported since v114
Safari - supported since Safari Technology Preview 166
/Bug to turn on by default/:
https://bugzilla.mozilla.org/show_bug.cgi?id=<https://bugzilla.mozilla.org/show_bug.cgi?id=1860446>1866993
<https://bugzilla.mozilla.org/show_bug.cgi?id=1866993>
Standard: https://html.spec.whatwg.org/#the-popover-attribute
Many thanks,
Ziran
--
You received this message because you are subscribed to the Google
Groups "[email protected]" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to [email protected].
To view this discussion on the web visit
https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/476fae4d-37af-4bf5-bd62-e737527a433e%40igalia.com
<https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/476fae4d-37af-4bf5-bd62-e737527a433e%40igalia.com?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google Groups
"[email protected]" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/0f8f9350-eaf4-4f52-831f-7c4fc6489245%40igalia.com.
