Closed
Bug 366880
Opened 19 years ago
Closed 19 years ago
Column bugs
Categories
(Core :: Layout, defect)
Core
Layout
Tracking
()
RESOLVED
FIXED
People
(Reporter: roc, Assigned: roc)
Details
Attachments
(2 files)
|
687 bytes,
text/html
|
Details | |
|
6.90 KB,
patch
|
dbaron
:
review+
dbaron
:
superreview+
|
Details | Diff | Splinter Review |
1) default column-gap is 0, the spec has been updated to make 1em the initial value.
2) The attached testcase shows that vertical margins screw up incremental reflow ... try resize the text in different directions.
| Assignee | ||
Comment 1•19 years ago
|
||
... as per latest columns draft.
Attachment #251612 -
Flags: superreview?(dbaron)
Attachment #251612 -
Flags: review?(dbaron)
Comment on attachment 251612 [details] [diff] [review]
support -moz-column-gap:normal and make it the initial value
r+sr=dbaron
Attachment #251612 -
Flags: superreview?(dbaron)
Attachment #251612 -
Flags: superreview+
Attachment #251612 -
Flags: review?(dbaron)
Attachment #251612 -
Flags: review+
Actually, could you also add support for eCSSUnit_Initial in the nsRuleNode.cpp changes?
Er, never mind, since that's actually pretty ugly in the current architecture.
| Assignee | ||
Comment 5•19 years ago
|
||
Checked in. The incremental reflow bug was filed as bug 367099.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Comment 6•19 years ago
|
||
So I was wondering... in getComputedStyle do we want to compute to the length as in this patch, or the keyword "normal"?
In general, the actual computed style is "normal", but in some cases getComputedStyle returns used style...
Just need to know so I can merge the patch for bug 365932 to this change.
I'll admit I'm a little biased because "normal" is easier to do. ;)
| Assignee | ||
Comment 7•19 years ago
|
||
I'm fine either way.
You need to log in
before you can comment on or make changes to this bug.
Description
•