Closed
Bug 486551
Opened 16 years ago
Closed 11 years ago
GTK native widgets ignore <meta http-equiv="msthemecompatible" value="no">
Categories
(Core :: Widget: Gtk, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 966240
People
(Reporter: zwol, Assigned: zwol)
Details
Attachments
(1 file)
979 bytes,
patch
|
roc
:
review+
|
Details | Diff | Splinter Review |
It's supposed to be possible to turn off native form controls for the entire document by putting <meta http-equiv="msthemecompatible" value="no"> in the HEAD. Or anyway we support that on Mac and Windows. But nsNativeThemeGTK doesn't check for it so on Linux the tag has no effect. This tripped me up testing the patch for bug 475535 (which regressed bug 373381, but I didn't see it because the tests use the above tag).
I'm a little dubious about whether we should support this at all, nowadays (it appears to be an IE6 compatibility hack), but given that we do it oughta be cross platform. And the flag in the pres shell that the tag sets might someday get set by other stuff too (I can see a hidden pref to disable native themes being useful if only for testing). Attached patch does this; I'm assuming that there is no problem with rendering any non-native widget on Linux given that for a long time it didn't *do* native controls.
Assignee | ||
Comment 1•16 years ago
|
||
Seems worth adding a reftest for this (comparing it to -moz-appearance:none).
I think we implemented support for this pretty recently, actually.
Attachment #370687 -
Flags: review?(roc) → review+
Assignee | ||
Comment 3•16 years ago
|
||
Problem with writing a reftest is, -moz-appearance:none doesn't work on <input type="file"> and makes <select> look ever so slightly different than it does with the meta tag. I suppose both of those are also bugs ...
![]() |
||
Comment 4•16 years ago
|
||
meta http-equiv="msthemecompatible" value="no" has been supported (Win/Mac) for a while, with many issues.
Bug 247161 on Windows, sorta fixed I think.
Bug 420363 on Mac, fixed by disabling 'msthemecompatible' for scroll bars, and bug 464876 for a 'better' fix.
I always wondered why this non-standard meta tag ought to supported. Neither Opera, nor WebKit Safari support it.
See also bug 322218.
Comment 5•16 years ago
|
||
I was looking for a bug about removing support for this tag. The code appears to be fairly old. The blame in CVS goes back to 2003 where it was refactored into the file it's in now. Seems like a pretty silly thing to support these days. It makes my page scrollbar non-themed, which is weird.
Assignee | ||
Comment 6•16 years ago
|
||
(In reply to comment #5)
> I was looking for a bug about removing support for this tag. The code appears
> to be fairly old. The blame in CVS goes back to 2003 where it was refactored
> into the file it's in now. Seems like a pretty silly thing to support these
> days.
I would support dropping it (cross-platform), FWIW. I can do an alternative patch to that effect.
> It makes my page scrollbar non-themed, which is weird.
That sounds like a bug - it should not affect chrome. (Maybe the page scrollbar is being treated as content?)
Updated•11 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•