Closed Bug 854393 Opened 13 years ago Closed 13 years ago

Update /l10n/ tests to mitigate the "Disconnect Error: Application unexpectedly closed" failure

Categories

(Mozilla QA Graveyard :: Mozmill Tests, defect)

defect
Not set
normal

Tracking

(firefox22 fixed, firefox23 fixed)

RESOLVED FIXED
Tracking Status
firefox22 --- fixed
firefox23 --- fixed

People

(Reporter: andrei, Assigned: andrei)

References

()

Details

Attachments

(1 file, 2 obsolete files)

Related to bug 831297 , but another regression. Fix should be trivial: update the pre and posthooks to accomodate the new Modal Window that is spawning.
Which new modal window are you talking about?
No longer blocks: 853865
I think I hurried a bit. Its not a new Modal Dialog, its the same as in bug 831297 (Restart Firefox) but the method it gets invoked has changed. I have that fixed, but I'm failing later on in another Pref Pane. Still need a bit of work.
Attached patch Patch v1 (obsolete) — Splinter Review
I have fixed the issue. But in doing so we opened another problem. When the "Privacy > History > Use custom settings for history > Always use private browsing mode" is checked the checkbox and button on the "Security > Passwords Remember password for sites (checkbox) + Exceptions (button)" are both disabled. Which would fail with a "Window has been found" error (we click on a disabled button). To mitigate this issue I moved the Security pane tests before the Privacy pane tests. This solves the problem, but I am not sure it is the best solution. We might uncheck the "Always use private browsing mode" before moving out of the Privacy pane. Any input on which solution would be better?
Attachment #728990 - Flags: feedback?(hskupin)
Attachment #728990 - Flags: feedback?(dave.hunt)
Comment on attachment 728990 [details] [diff] [review] Patch v1 Review of attachment 728990 [details] [diff] [review]: ----------------------------------------------------------------- This is more a needinfo as a feedback request. Please distinct between both. As you have already mentioned do not flip the order but reset everything we have modified in the privacy pane. Otherwise we will run into problems all over the place. If that doesn't work at the moment our post handler is not working as expected. Please also update the summary of the bug so we can identify it beside all the other application disconnected bugs. Thanks.
Attachment #728990 - Flags: feedback?(hskupin)
Attachment #728990 - Flags: feedback?(dave.hunt)
Attachment #728990 - Flags: feedback-
Attached patch Patch v2 (obsolete) — Splinter Review
Fixed the issue. Updated hooks to retain all commands except the one causing the Restart Dialog.
Attachment #728990 - Attachment is obsolete: true
Attachment #731883 - Flags: review?
Attached patch Patch v2Splinter Review
Fixed the issue. Updated hooks to retain all commands except the one causing the Restart Dialog.
Attachment #731883 - Attachment is obsolete: true
Attachment #731883 - Flags: review?
Attachment #731885 - Flags: review?(andreea.matei)
Comment on attachment 731885 [details] [diff] [review] Patch v2 Review of attachment 731885 [details] [diff] [review]: ----------------------------------------------------------------- This tests well for me, but I'd like a second opinion from Henrik, if there's something we should do different. Also please change the summary of the bug as requested above.
Attachment #731885 - Flags: review?(andreea.matei) → review+
Summary: Failure in testAccessKeys/test1.js - "Disconnect Error: Application unexpectedly closed" → Update /l10n/ tests to mitigate the "Disconnect Error: Application unexpectedly closed" failure
Attachment #731885 - Flags: review+ → review?(hskupin)
Comment on attachment 731885 [details] [diff] [review] Patch v2 Review of attachment 731885 [details] [diff] [review]: ----------------------------------------------------------------- If that fixes the problem and let us successfully run the tests, I'm happy with this change. But we should file a follow-up bug to let us disable actions on specific elements. In this case the autostart pb mode. I don' see a reason why we have to click on it. It doesn't change the ui elements in terms of that accesskeys are affected. Please land on default and aurora at the same time.
Attachment #731885 - Flags: review?(hskupin)
Attachment #731885 - Flags: review+
Attachment #731885 - Flags: checkin?(andreea.matei)
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Attachment #731885 - Flags: checkin?(andreea.matei) → checkin+
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: