Closed Bug 858203 Opened 12 years ago Closed 12 years ago

mark more reftests as needs-focus

Categories

(Core :: General, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla23

People

(Reporter: froydnj, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

No description provided.
In service of bug 813742, this patch attempts to identify all the reftests that need focus and aren't marked as such. Testing methodology: 1. Start headless X server. Start basic window manager on it. 2. Run reftests with said X server. Take note of failing tests. 3. Disable all reftests that need focus: find $topsrcdir -name '*.list' | xargs sed -i -e '/needs-focus/s/^/#/' 4. Make reftest.js:Focus never focus the window and always return true. 5. Start reftests with said X server again. Once the tests begin running, start a xterm on the same X server. The window manager will focus this xterm and will not return focus to the browser. 6. Compare now-failing tests with baseline. Mark all such tests as needs-focus. Comments on specific tests: editor/reftests/ - spellcheck-input-ref.html and spellcheck-textarea-ref.html focus input elements and don't work right without the window having focus. - spellcheck-hyphen-invalid-ref.html and spellcheck-hyphen-multiple-invalid-ref.html use @autofocus on textarea. - 674212-spellcheck.html, 338427-2.html, and 462758-grabbers-resizers.html all wait for onfocus for div elements. layout/reftests/bugs/ - 652301-1b.html focuses a bogus element with an onfocus handler. layout/reftests/selection/ - pseudo-element-of-native-anonymous-ref.html .select()s an <input>.
Attachment #733498 - Flags: review?(dholbert)
Comment on attachment 733498 [details] [diff] [review] mark more reftests as needs-focus Methodology seems sound. I didn't look at all of the flagged /editor tests, but I buy that they need focus, given that they're using <input> elements and given your comments.
Attachment #733498 - Flags: review?(dholbert) → review+
(Technically Testing|Reftest is for bugs in the reftest *harness*, not in tests/manifests. Moving this to Core|General.)
Component: Reftest → General
Product: Testing → Core
Version: unspecified → Trunk
It would be cool if we could add something to the reftest harness to explicitly *not* focus tests that aren't marked as needs-focus, to prevent these from creeping in.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla23
Blocks: 859339
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: