Closed Bug 1097419 Opened 10 years ago Closed 10 years ago

[Calendar][Text Selection] Selection bubble doesn't appear on account login

Categories

(Core :: DOM: Selection, defect, P2)

defect

Tracking

()

RESOLVED FIXED
mozilla37

People

(Reporter: m_kato, Assigned: mtseng)

References

Details

Attachments

(2 files, 5 obsolete files)

I think z-index seems to be too large for oauth2 screen. Please adjust z-index for text selection bubble. Also, z-index will be incremented by bug 1095320. - Step 1. Launch Calendar 2. Open [Calendar Settings] 3. Tap [Accounts] 4. Tap [Google] 5. Tap [Email] field, then input 'aaa' 6. Long tap 'aaa' to launch selection bubble - Result Selection bubble disappears - Expected Result Selection bubble appears
This is a 2.2 feature.
feature-b2g: --- → 2.2+
correction, this is bug not feature.
feature-b2g: 2.2+ → ---
Priority: -- → P2
This issue is still existed on master.
George, I think this is zorder issue becasue I saw gecko did send out the selectionstatechange to sys app.
Flags: needinfo?(gduan)
In today's build, I put console.log in https://github.com/mozilla-b2g/gaia/blob/master/apps/system/js/text_selection_dialog.js#L119 but I cannot get any msg, so, I assume gaia cannot get selectionstatechanged event from gecko too.
Flags: needinfo?(gduan)
(In reply to George Duan [:gduan] [:喬智] from comment #5) > In today's build, I put console.log in > https://github.com/mozilla-b2g/gaia/blob/master/apps/system/js/ > text_selection_dialog.js#L119 > but I cannot get any msg, so, I assume gaia cannot get selectionstatechanged > event from gecko too. After checking, the event couldn't pass successfully from BrowserElementParent to Shell.js. That's why gaia couldn't receive the dom event changes.
doesn't look like this bug belongs to the calendar team (since it also happens on email). we should assign it to the correct team.
Flags: needinfo?(gduan)
Component: Gaia::Calendar → Selection
Flags: needinfo?(gduan)
Product: Firefox OS → Core
Assignee: nobody → mtseng
Comment on attachment 8539152 [details] [diff] [review] Part 1: Handle nested mozbrowser iframe for selectionstatechanged, touchcarettap and scrollviewchange v2. Review of attachment 8539152 [details] [diff] [review]: ----------------------------------------------------------------- Redirecting to Kan-Ru since he owns this code!
Attachment #8539152 - Flags: review?(fabrice) → review?(kchen)
Comment on attachment 8539153 [details] [diff] [review] Part 2: Add mochitest for nested mozbrowser iframe case. Review of attachment 8539153 [details] [diff] [review]: ----------------------------------------------------------------- Redirecting to Kan-Ru since he owns this code!
Attachment #8539153 - Flags: review?(fabrice) → review?(kchen)
Comment on attachment 8539153 [details] [diff] [review] Part 2: Add mochitest for nested mozbrowser iframe case. Review of attachment 8539153 [details] [diff] [review]: ----------------------------------------------------------------- ::: dom/browser-element/mochitest/browserElement_CopyPaste.js @@ +14,5 @@ > +// Give our origin permission to open browsers, and remove it when the test is complete. > +var principal = SpecialPowers.wrap(document).nodePrincipal; > +SpecialPowers.addPermission("browser", true, { url: SpecialPowers.wrap(principal.URI).spec, > + appId: principal.appId, > + isInBrowserElement: true }); Could you use SpecialPowers.pushPermissions?
Attachment #8539153 - Flags: review?(kchen) → review+
Comment on attachment 8539152 [details] [diff] [review] Part 1: Handle nested mozbrowser iframe for selectionstatechanged, touchcarettap and scrollviewchange v2. Review of attachment 8539152 [details] [diff] [review]: ----------------------------------------------------------------- Does that mean multiple BrowserParents could receive these events? Is that expected?
Set useCapture to ture, so nested mozbrowser iframe would send selectionstatechanged, touchcarettap and scrollviewchange event to top most mozbrowser iframe only.
Attachment #8539152 - Attachment is obsolete: true
Attachment #8539152 - Flags: review?(kchen)
Attachment #8540604 - Flags: review?(kchen)
Addressed to reviewer's comment.
Attachment #8539153 - Attachment is obsolete: true
(In reply to Kan-Ru Chen [:kanru] from comment #16) > Comment on attachment 8539152 [details] [diff] [review] > Part 1: Handle nested mozbrowser iframe for selectionstatechanged, > touchcarettap and scrollviewchange v2. > > Review of attachment 8539152 [details] [diff] [review]: > ----------------------------------------------------------------- > > Does that mean multiple BrowserParents could receive these events? Is that > expected? No, this is not expected. I updated my patch to address this problem. Could you review it again? Thanks!
Comment on attachment 8540605 [details] [diff] [review] Part 2: Add mochitest for nested mozbrowser iframe case v2. (carry r+: kanru) Review of attachment 8540605 [details] [diff] [review]: ----------------------------------------------------------------- ::: dom/browser-element/mochitest/browserElement_CopyPaste.js @@ +16,5 @@ > +var context = { 'url': SpecialPowers.wrap(principal.URI).spec, > + 'appId': principal.appId, > + 'isInBrowserElement': true }; > +SpecialPowers.pushPermissions([ > + {'type': 'browser', 'allow': 1, 'context': context}]); Sorry, this is not correct. SpecialPowers.pushPermissions needs a callback as second argument. Usually it's the runTest function. In this test you could use addEventListener('testready', function() { SpecialPowers.pushPermissions([ {'type': 'browser', 'allow': 1, 'context': context} ], runTest); });
Attachment #8540605 - Flags: review-
Use callback of pushPermissions to run test.
Attachment #8540605 - Attachment is obsolete: true
Attachment #8541038 - Flags: review?(kchen)
Attachment #8540604 - Flags: review?(kchen) → review+
Attachment #8541038 - Flags: review?(kchen) → review+
Thanks for review. \o/
Keywords: checkin-needed
Backed out for B2G mochitest timeouts. https://hg.mozilla.org/integration/mozilla-inbound/rev/088cfed82c74 https://treeherder.mozilla.org/logviewer.html#?job_id=4957550&repo=mozilla-inbound 08:44:37 INFO - 508 INFO TEST-PASS | dom/browser-element/mochitest/test_browserElement_inproc_CopyPaste.html | A valid string reason is expected 08:44:37 INFO - 509 INFO TEST-PASS | dom/browser-element/mochitest/test_browserElement_inproc_CopyPaste.html | Reason cannot be empty 08:44:37 INFO - 510 INFO TEST-UNEXPECTED-FAIL | dom/browser-element/mochitest/test_browserElement_inproc_CopyPaste.html | Test timed out. - expected PASS Same for OOP.
Fix b2g emulator test fail.
Attachment #8541038 - Attachment is obsolete: true
Comment on attachment 8543867 [details] [diff] [review] Part 2: Add mochitest for nested mozbrowser iframe case v4. Kanru, Please review it again. Thanks The main difference is adding a "isChildProcess" function and check it at testSelectAll function.
Attachment #8543867 - Flags: review?(kchen)
Attachment #8543867 - Flags: review?(kchen) → review+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: