Closed
Bug 379303
Opened 18 years ago
Closed 8 years ago
Make dashed/dotted border rendering pretty again
Categories
(Core :: Layout, defect, P5)
Tracking
()
RESOLVED
FIXED
People
(Reporter: vlad, Unassigned)
References
Details
(Keywords: regression, Whiteboard: [dbaron-1.9:RwCo])
Attachments
(3 files)
As part of the landing of bug 368247 dashed and dotted borders aren't as pretty as they used to be, especially at thick border widths in a small space. This should be fixed; it should not be an especially complicated fix, just some extra logic in creating the paths.
Reporter | ||
Comment 1•18 years ago
|
||
example.
Reporter | ||
Comment 2•18 years ago
|
||
The stuff in bug 19963 should be considered when fixing this, if possible.
Updated•18 years ago
|
Flags: blocking1.9?
Updated•18 years ago
|
Flags: blocking1.9? → blocking1.9+
Updated•17 years ago
|
Whiteboard: [dbaron-1.9:RwCo]
Priority: -- → P5
Updated•17 years ago
|
Keywords: regression
In FF3 the top border of an element is rendered with a smaller height if:
* the DIV is empty and
* border-top-style is not (dotted or dashed) and
border-bottom-style is (dotted or dashed) and * border-top-width is greater than border-bottom-width
Attachment #303034 -
Attachment description: if → In FF3 the top border of an element is rendered with a smaller height if the DIV is empty and border-top-style is not (dotted or dashed) and border-bottom-style is (dotted or dashed) and border-top-width is greater than border-bottom-width
The previous comment was filed as bug 417246, which should block.
I think this one shouldn't block, although I'll leave it wanted.
Flags: wanted1.9+
Flags: blocking1.9-
Updated•17 years ago
|
Flags: tracking1.9+
Flags: wanted1.9-
Flags: wanted1.9+
Flags: wanted-next+
This is essentially the same bug as https://bugzilla.mozilla.org/show_bug.cgi?id=19963.
That bug has the highest priority of all dotted-border-corners-ugly related bugs. It is also the oldest and it has a (seemingly active) developer assigned to it.
I suggest to "merge" this bug with 19963. If you care, please check it out and vote for it.
Comment 7•16 years ago
|
||
It's not quite the same bug. Fixing that bug might fix this one, but this one can be fixed without fixing the other, really, since this one is a recent regression and the other clearly is not.
Depends on: 19963
Comment 8•16 years ago
|
||
IMO it doesn't make sense to do anything but fix the entire problem at one go. I hope to get back to bug 19963 this week.
Reporter | ||
Updated•15 years ago
|
Assignee: vladimir → nobody
Comment 9•8 years ago
|
||
Fixed as a part of bug 382721.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•