Closed
Bug 469166
Opened 16 years ago
Closed 10 years ago
css property cursor has value of none when it should have auto
Categories
(Firefox for Android Graveyard :: General, defect)
Firefox for Android Graveyard
General
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: jmaher, Unassigned)
References
Details
Attachments
(1 file)
2.71 KB,
text/html
|
Details |
While running mochitests, the layout/style/test directory has about 15 tests that fail. After investigation, we found that the css property "cursor" was not able to have a default value of "auto", instead it has "none".
If I set user_pref("browser.ui.cursor", true), I see the test pass.
This brings up a question as to if we are supporting all CSS tags properly. If we are or have made this on purpose, then we need to fix the test cases.
Comment 1•16 years ago
|
||
It seems to work for chrome elements when I test it with this testcase.
Comment 2•16 years ago
|
||
We do this intentionally, yeah:
http://mxr.mozilla.org/mobile-browser/source/chrome/content/content.css
There's probably a better way of doing this.
Comment 3•16 years ago
|
||
Oh, yes, I see it here now:
http://mxr.mozilla.org/mobile-browser/source/chrome/content/browser.js#142
Do you do this as a workaround for bug 309547 or something?
Comment 4•16 years ago
|
||
Yeah, I guess that would be the alternate way.
Comment 5•10 years ago
|
||
This bug has been buried in the graveyard and has not been updated in over 5 years. It is probably safe to assume that it will never be fixed, so resolving as WONTFIX.
[Mass-change filter: graveyard-wontfix-2014-09-24]
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•