Closed Bug 1496074 Opened 7 years ago Closed 3 years ago

Google Search custom selects are broken on firefox because of unprefixed 'appearance' rule.

Categories

(Web Compatibility :: Site Reports, defect, P1)

Firefox 62
Desktop
All

Tracking

(firefox101 affected)

RESOLVED FIXED
Tracking Status
firefox101 --- affected

People

(Reporter: earle.timothy, Assigned: skyschub, NeedInfo)

References

()

Details

(Keywords: webcompat:site-wait, Whiteboard: [sitewait][webcompat:sightline])

Attachments

(1 file)

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36 Steps to reproduce: Navigate to any site with custom CSS for select or text entries. Google, or anything using bootstrap Actual results: Styles/custom controls aren't honored. Instead they are replaced with a motif-like representation of the control Expected results: Use/render the controls as desired and performed by other browsers (Chrome, Safari, etc.) or default to a look and feel from this century.
Component: Untriaged → CSS Parsing and Computation
Product: Firefox → Core
Sigh, this looks like a regression on Google search, not on Firefox. The page renders wrong in FF57 as well for example. STR would be something like searching: "One second to minutes" in Google. They're serving to Chrome: -webkit-appearance:button; appearance:button; In an inline style. They're serving to Firefox: appearance:button;appearance:button; Note that they're both unprefixed. No browser supports the unprefixed version of appearance... Adam, could you contact Google about this so that they serve the right prefix?
Status: UNCONFIRMED → NEW
Component: CSS Parsing and Computation → Desktop
Ever confirmed: true
Flags: needinfo?(astevenson)
Product: Core → Tech Evangelism
Summary: custom CSS styles downgrade in a very ugly manner → Google Search custom selects are broken on firefox because of unprefixed 'appearance' rule.
Version: 62 Branch → Firefox 62
FYI Philip, in case you have a quicker route to report issues to GWS folks. (see STR in Comment #1)
Flags: needinfo?(philip)
Priority: -- → P1
See bug 1368555 comment 40 for this Google issue ( https://webcompat.com/issues/7309 ). It looks like I didn't spin off a separate bug for that though, so this one is good.
That said, I think the bug as originally reported is basically bug 1481591 and bug 1481594. Given that we have those bugs open we could still use this bug for the specific problem of Google serving broken CSS to Firefox though.
Sent an email to our partner mailing list.
Flags: needinfo?(astevenson)
Whiteboard: [sitewait]
Product: Tech Evangelism → Web Compatibility

See bug 1547409. Moving webcompat whiteboard tags to keywords.

Flags: needinfo?(philip)

I was able to reproduce the issue using other devices as well. Performing a basic conversion on google.com returns the result, but the result can not be editable, unlike Chrome. For instance, in my case, I have to perform a new search if I want to find out how many liters are in 100 ounces of fluid. Google lets you to edit the search query, by altering the quantity:

https://prnt.sc/0Cfg-hEwq19T

Tested with:

Browser / Version: Firefox Nightly 101.0a1 (2022-04-27) (64-bit) / Chrome Version Version 101.0.4951.41 (Official Build) (64-bit)
Operating System: Windows 10 PRO x64
Operating System: Mac OSX 10.15.6

Assignee: nobody → dschubert
Status: NEW → ASSIGNED
OS: Unspecified → All
Hardware: Unspecified → Desktop
Severity: normal → S3

The issue is no longer reproducible: https://prnt.sc/efSpfJyLgWkL

Tim, is the issue fixed on your side?

Tested with:

Browser / Version: Firefox Nightly 110.0a1 (2023-01-16) (64-bit)
Operating System: Windows 10 PRO x64
Operating System: Mac OSX Catalina 10.15.7

Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Flags: needinfo?(earle.timothy)
Resolution: --- → FIXED
Whiteboard: [sitewait] → [sitewait][webcompat:sightline]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: