Last modified: 2014-09-22 14:45:27 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T66775, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 64775 - OOjs UI: Dialog emits "closing" event 250ms after close() is invoked
OOjs UI: Dialog emits "closing" event 250ms after close() is invoked
Status: RESOLVED FIXED
Product: OOjs UI
Classification: Unclassified
General (Other open bugs)
unspecified
All All
: Normal normal
: ---
Assigned To: Editing team bugs – take if you're interested!
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2014-05-02 23:35 UTC by Juliusz Gonera
Modified: 2014-09-22 14:45 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Juliusz Gonera 2014-05-02 23:35:41 UTC 
That's because the event is emitted by the parent method (Window#close), which is called with a delay of 250ms.

Talked to Trevor, reporting on bugzilla just to keep track of it.
Comment 1 Bartosz Dziewoński 2014-09-22 14:45:27 UTC 
This seems to have been fixed, perhaps in the great and terrible dialog refactor (3ba36b9a53aa41da07c3b56a063fe0d3c419c2a5). It has definitely become irrelevant since Windows, and this Dialogs, no longer emit any events anymore.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links