Closed
Bug 455818
Opened 17 years ago
Closed 17 years ago
Some editor movement tests need to be fixed for Windows
Categories
(Core :: DOM: Editor, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: roc, Assigned: MatsPalmgren_bugz)
References
Details
Attachments
(3 files)
|
9.28 KB,
patch
|
Details | Diff | Splinter Review | |
|
4.50 KB,
patch
|
roc
:
review+
|
Details | Diff | Splinter Review |
|
9.32 KB,
patch
|
Details | Diff | Splinter Review |
See https://bugzilla.mozilla.org/show_bug.cgi?id=454004#c29. The failing tests have been disabled temporarily.
| Assignee | ||
Comment 1•17 years ago
|
||
There were two problems with the tests, the first was due to the difference
in the default value for the pref "layout.word_select.eat_space_to_next_word"
between platforms, which affects "cmd_selectWordNext".
The second problem was caused by font/line-height differences which affects
how many lines to scroll for a page scroll.
I wrapped all the commands that involves selection in a function and
run it twice (eat_space_to_next_word=true/false) to check that only
"cmd_selectWordNext" is affected (and with correct values for each).
The second problem was fixed by hard-coding some font-size/line-height
etc styles. (I also fixed a few Windows ^M line-endings)
The test now passes on Windows/Linux/MacOSX for me.
Assignee: nobody → mats.palmgren
| Assignee | ||
Comment 2•17 years ago
|
||
Attachment #339257 -
Flags: review?(roc)
| Reporter | ||
Comment 3•17 years ago
|
||
Comment on attachment 339257 [details] [diff] [review]
Patch rev. 1 (diff -uw)
Looks good. Only thing I'd add is some exception-catching so that if we throw an exception during the test the pref value is restored to its original value.
Attachment #339257 -
Flags: review?(roc) → review+
| Reporter | ||
Comment 4•17 years ago
|
||
Thanks a lot!
| Assignee | ||
Comment 5•17 years ago
|
||
Wrapped the pref changes in a try-finally block to address comment 3.
| Assignee | ||
Comment 6•17 years ago
|
||
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•