1502150 - getComputedStyle difference between Fennec and Desktop (at least for WebkitAppearance values)

Status: RESOLVED DUPLICATE of bug 1618202

(Core :: Layout, defect, P3)

Description

[Mike Taylor [:miketaylr]]

Attachment: computed-appearance.html

STR:

In Fennec and Desktop, open the test case. 

Expected: See PASS (which is what I see in Desktop)
Actual: In Fennec, I get FAIL in Nightly 65.

For convenience, here's the content of the test case:

var f = document.createElement("button")
f.style["-webkit-appearance"] = "button"
var computed = getComputedStyle(f).WebkitAppearance
if (computed == "button") {
    document.write("PASS");
} else {
    document.write("FAIL");
}

Comment 1

[Wes Kocher (:KWierso) (Not reading bugmail; email directly if needed)]

FWIW, Firefox Focus with Geckoview also shows FAIL in that test case.

Comment 2

[Jonathan Watt [:jwatt]]

Emilio, are we taking different code paths for style for fennec for some reason?

Comment 3

[Emilio Cobos Álvarez (:emilio)]

Nope, most likely this:

  https://searchfox.org/mozilla-central/rev/e0c879c86b95bdc752b1dbff6088169735674e4a/mobile/android/themes/geckoview/content.css#97

I don't know who maintains those stylesheets, but they're somewhat broken... See also bug 1470709 for an example.

Comment 4

[Firefox Bug Husbandry Bot]

Migrating Webcompat whiteboard priorities to project flags. See bug 1547409.

Comment 5

[Firefox Bug Husbandry Bot]

See bug 1547409. Migrating whiteboard priority tags to program flags.

Comment 6

[Chris Peterson [:cpeterson]]

(In reply to Emilio Cobos Álvarez (:emilio) from comment #3)

https://searchfox.org/mozilla-central/rev/
e0c879c86b95bdc752b1dbff6088169735674e4a/mobile/android/themes/geckoview/
content.css#97

I don't know who maintains those stylesheets, but they're somewhat broken...
See also bug 1470709 for an example.

Emilio, who do you think should maintain these Android content stylesheets? The Gecko Layout/CSS team? A mobile UX designer?

Comment 7

[Emilio Cobos Álvarez (:emilio)]

Probably the layout team, but I don't know why the stylesheets look like they do right right now. Most of them look like workarounds for form control issues that should be fixed by the android folks.

Comment 8

[Chris Peterson [:cpeterson]]

stylesheets ... workarounds for form control issues that should be fixed by the android folks.

Removing bug priority to send bug back to GV triage for discussion of these form control issues.

Probably the layout team, but I don't know why the stylesheets look like they do right right now.

And whether we should move this bug from the GeckoView component to Layout.

Comment 9

[Chris Peterson [:cpeterson]]

Moving from GeckoView's Bugzilla component to Layout because this is a layout webcompat issue.

I'm not sure which team should be responsible for deciding what Gecko's Android content stylesheets should look like. The Layout engineering team? The GeckoView engineer team? A Fenix product manager or UX designer?

firefox-esr68=wontfix because we wouldn't uplift a fix for this bug to Fennec ESR 68.

Comment 10

[BugBot [:suhaib / :marco/ :calixte]]

The priority flag is not set for this bug.
:kamidphish, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 11

[Emilio Cobos Álvarez (:emilio)]

This was fixed by bug 1618202.