Closed
Bug 713376
Opened 13 years ago
Closed 13 years ago
Comment popup appearance broken by bug 497995 landing
Categories
(Tree Management Graveyard :: TBPL, defect)
Tree Management Graveyard
TBPL
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: philor, Assigned: philor)
References
Details
Attachments
(1 file, 1 obsolete file)
979 bytes,
patch
|
mstange
:
review+
|
Details | Diff | Splinter Review |
Apparently the border-image spec changed, and now we need to say that we want the comment popup to be filled, rather than wanting it to look like unreadable crap. Chrome is using unprefixed, I don't actually know whether or not there are versions of either Chrome or Safari that used an updated version of -webkit prefixed, but it's probably better to spew even more parsing errors than to leave something looking like crap.
Attachment #584205 -
Flags: review?(mstange)
Comment 1•13 years ago
|
||
Comment on attachment 584205 [details] [diff] [review] fix v.1 Review of attachment 584205 [details] [diff] [review]: ----------------------------------------------------------------- ::: css/style.css @@ +731,5 @@ > border: solid transparent; > border-width: 10px 18px 25px; > } > .popupForm:nth-child(1n) { > -moz-border-image: url(../images/hudborderimage.png) 10 18 25 repeat; So we need to keep the old version around for backward compat reasons? Otherwise looks fine.
Assignee | ||
Comment 2•13 years ago
|
||
Right: every version of Firefox from today's nightly back through whenever we start working, Fx2 maybe, reads that line, and nightlies dated 2011-12-23 or earlier, Fx11, Fx10, etc., say "okay, I'll make an uncrappy comment form out of that." Today's nightly says "oh, you want a tiny border, and white-on-white text, okay." Then everything but today's nightly reads the next line with "fill" and says "parsing error, declaration dropped" while today's nightly says "oh, you want to be able to read the comment form, okay, we'll do that instead."
Comment 3•13 years ago
|
||
Oh the joy of using experimental vendor prefixes. I guess we will have to live with it until someday when we can just drop them altogether.
Updated•13 years ago
|
Attachment #584205 -
Flags: review?(mstange) → review+
Assignee | ||
Comment 4•13 years ago
|
||
http://hg.mozilla.org/users/mstange_themasta.com/tinderboxpushlog/rev/a9d51f2493da
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Comment 5•13 years ago
|
||
While waiting for the fix to land on the production server, I developed this userContent.css hack. Sharing it here in case it helps others.
Comment 6•13 years ago
|
||
(In reply to Bill Gianopoulos from comment #5) > Created attachment 584254 [details] > Workaround > > While waiting for the fix to land on the production server, I developed this > userContent.css hack. Sharing it here in case it helps others. Well, that does not work as well as I thought. Makes the popup display more or less correctly, but prevents the drag and drop to add builds to the comment from working.
Updated•13 years ago
|
Attachment #584254 -
Attachment is obsolete: true
Updated•10 years ago
|
Product: Webtools → Tree Management
Updated•9 years ago
|
Product: Tree Management → Tree Management Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•