Closed
Bug 1040936
Opened 11 years ago
Closed 11 years ago
(system-dialog) [Window Management] Improve interoperability between system dialogs and value selectors.
Categories
(Firefox OS Graveyard :: Gaia::System::Window Mgmt, defect)
Tracking
(blocking-b2g:2.1+, b2g-v2.1 verified)
Tracking | Status | |
---|---|---|
b2g-v2.1 | --- | verified |
People
(Reporter: yzen, Assigned: yzen)
References
Details
Attachments
(1 file)
Currently there are several visibility issues between the system dialogs and the value selectors, in particular related to the z-index of the overlay dialog and the corresponding app's value-selector (such as the issue described in bug 1040290). The proper solution is to:
* have systemDialogManager get the mozChromeEvent, and stop propagation to avoid AppWindowManager getting it.
* dispatch the event to the active system dialog.
* do what we do in appWindow: install value-selector, call setVisible of system dialog (not implemented now)
* and we will need to the same thing again for other window managers if their window needs value selector.
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → yzenevich
Assignee | ||
Comment 1•11 years ago
|
||
Attachment #8468209 -
Flags: review?(alive)
Comment 2•11 years ago
|
||
Comment on attachment 8468209 [details] [review]
Github pull request.
Yura, nice done.
I have some comments on github, lemme know if you have question to fix them. Thank you very much!
Attachment #8468209 -
Flags: review?(alive) → feedback+
Assignee | ||
Comment 3•11 years ago
|
||
Comment on attachment 8468209 [details] [review]
Github pull request.
All comments addressed. Marking for re-review.
Attachment #8468209 -
Flags: review?(alive)
Comment 4•11 years ago
|
||
Comment on attachment 8468209 [details] [review]
Github pull request.
Thank you very much!
Attachment #8468209 -
Flags: review?(alive) → review+
Assignee | ||
Comment 5•11 years ago
|
||
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
status-b2g-v2.1:
--- → fixed
Target Milestone: --- → 2.1 S2 (15aug)
Comment 7•10 years ago
|
||
This issue has been verified successfully on Flame 2.1,we also checked bug 1040290,there is no same issue found on other page,so I think it is fixed.
Flame 2.1 build:
Gaia-Rev 77c57eb8a985d5cbd34a597fb1b978ba6e205af6
Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/f05d0a2d2378
Build-ID 20150120001202
Version 34.0
Device-Name flame
FW-Release 4.4.2
FW-Incremental eng.cltbld.20150120.035022
FW-Date Tue Jan 20 03:50:33 EST 2015
Bootloader L1TC000118D0
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•