Closed
Bug 1127778
Opened 11 years ago
Closed 10 years ago
Switching to reader mode changes paragraph display order
Categories
(Toolkit :: Reader Mode, defect, P3)
Tracking
()
RESOLVED
FIXED
Iteration:
39.2 - 23 Mar
People
(Reporter: capella, Assigned: Gijs)
References
(Blocks 2 open bugs)
Details
Attachments
(1 file, 2 obsolete files)
(Minor annoyance finally documented).
Using a simple 3-paragraph test [1], you can observe the order of paragraphs changing before [2] and after [3] entering readerMode.
[1] https://www.dropbox.com/s/0n0bec8x4p7i1je/readerReorder.html?dl=0
[2] https://www.dropbox.com/s/9msitzhmsw12o24/readerReorderBefore.png?dl=0
[3] https://www.dropbox.com/s/4q8mbuvgut3o79s/readerReorderAfter.png?dl=0
Comment 1•11 years ago
|
||
Is this bug 809724?
Reporter | ||
Comment 2•11 years ago
|
||
Sounds like it.
Comment 3•11 years ago
|
||
Using different tags. I don't think duping is the right process here.
See Also: → 809724
Updated•11 years ago
|
Updated•10 years ago
|
Priority: -- → P3
Comment 4•10 years ago
|
||
Minimal test case here: https://people.mozilla.org/~bnicholson/test/reader.html
This isn't a dupe of bug 809724 if that bug is due to mismatched tags (https://bugzilla.mozilla.org/show_bug.cgi?id=809724#c6). The test case linked above passes HTML validation.
Comment 5•10 years ago
|
||
Interestingly, simply adding a byline fixes the order in this case: https://people.mozilla.org/~bnicholson/test/reader2.html
Assignee | ||
Comment 6•10 years ago
|
||
This is because of the paging divs which somehow end up gathering up the other paras but not the second one, which then breaks stuff. In fact, I suspect I know what is the issue here (hint: removing things from an array you're looping over without being careful causes issues). Taking.
Assignee: nobody → gijskruitbosch+bugs
Status: NEW → ASSIGNED
Iteration: --- → 39.2 - 23 Mar
Points: --- → 5
Flags: qe-verify-
Flags: in-testsuite?
Flags: firefox-backlog+
Assignee | ||
Comment 7•10 years ago
|
||
Attachment #8578684 -
Flags: review?(bnicholson)
Assignee | ||
Comment 8•10 years ago
|
||
Because logging is turned off anyway, I'd like to just land this change, too, so we don't have to add our own impromptu logging all the time when we investigate quality issues this week.
Attachment #8578685 -
Flags: review?(bnicholson)
Assignee | ||
Comment 9•10 years ago
|
||
(because there is also a github repo, I don't really know if this needs to go here or on github, but considering I'm working with the desktop codebase, I've assumed 'here' for now, please let me know ASAP if that assumption is broken)
Assignee | ||
Comment 10•10 years ago
|
||
Attachment #8578684 -
Attachment is obsolete: true
Attachment #8578685 -
Attachment is obsolete: true
Attachment #8578684 -
Flags: review?(bnicholson)
Attachment #8578685 -
Flags: review?(bnicholson)
Attachment #8578755 -
Flags: review?(margaret.leibovic)
Comment 11•10 years ago
|
||
Comment on attachment 8578755 [details] [review]
PR
I already merged this on github. r+
Attachment #8578755 -
Flags: review?(margaret.leibovic) → review+
Assignee | ||
Updated•10 years ago
|
Assignee | ||
Updated•10 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•