Closed
Bug 953438
Opened 12 years ago
Closed 12 years ago
Change nsIFrame::HasTerminalNewline to HasSignificantTerminalNewline
Categories
(Core :: Layout, defect)
Tracking
()
RESOLVED
FIXED
mozilla29
People
(Reporter: roc, Assigned: roc)
References
Details
Attachments
(1 file)
|
9.86 KB,
patch
|
jfkthame
:
review+
|
Details | Diff | Splinter Review |
No description provided.
| Assignee | ||
Comment 1•12 years ago
|
||
Attachment #8351734 -
Flags: review?(jfkthame)
Comment 2•12 years ago
|
||
Comment on attachment 8351734 [details] [diff] [review]
fix
Review of attachment 8351734 [details] [diff] [review]:
-----------------------------------------------------------------
::: layout/generic/nsFrame.cpp
@@ +6355,5 @@
> endOfLine, 0);
> FrameContentRange range = GetRangeForFrame(targetFrame.frame);
> aPos->mResultContent = range.content;
> aPos->mContentOffset = endOfLine ? range.end : range.start;
> + if (endOfLine && targetFrame.frame->HasSignificantTerminalNewline()) {
At this callsite, there wasn't originally a check for StyleText()->NewlineIsSignificant(), so this changes the logic here. Are there examples where this will lead to an actual change in behavior?
Comment 3•12 years ago
|
||
yes, bug 947170
Updated•12 years ago
|
Attachment #8351734 -
Flags: review?(jfkthame) → review+
Updated•12 years ago
|
Keywords: checkin-needed
Comment 5•12 years ago
|
||
Keywords: checkin-needed
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla29
You need to log in
before you can comment on or make changes to this bug.
Description
•