Closed
Bug 593755
Opened 14 years ago
Closed 14 years ago
Blur of <browser> within chrome process does not blur <element> within <browser> object
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(fennec-)
RESOLVED
WONTFIX
Tracking | Status | |
---|---|---|
fennec | - | --- |
People
(Reporter: jbos, Assigned: jbos)
References
Details
Attachments
(1 file, 2 obsolete files)
1.16 KB,
patch
|
Details | Diff | Splinter Review |
In Meego we want to synchronize the chrome and the content processes focusmanager.
Which means:
In case the <browser> object gets blured we want to blur the element within the <browser> and set the focus within the browser back to content.
Assignee | ||
Comment 1•14 years ago
|
||
This is a way to fix the issue.
It simply connect the blur and foxus event to the blur and focus IPDL Message. Blur in content.js gets extended with a clearFocus(content);
Attachment #472334 -
Flags: review?(mark.finkle)
Comment 2•14 years ago
|
||
Comment on attachment 472334 [details] [diff] [review]
Version 1
>diff --git a/chrome/content/browser.js b/chrome/content/browser.js
> let browsers = document.getElementById("browsers");
> browsers.addEventListener("command", this._handleContentCommand, true);
> browsers.addEventListener("DOMUpdatePageReport", gPopupBlockerObserver.onUpdatePageReport, false);
>+ browsers.addEventListener("focus", function() {
>+ selectedBrowser().messageManager.messageManager.sendAsyncMessage("Browser:Focus",{});
>+ }, true);
>+ browsers.addEventListener("blur", function() {
>+ selectedBrowser().messageManager.messageManager.sendAsyncMessage("Browser:Blur",{});
>+ }, true);
Browser.selectedBrowser.messageManager.sendAsyncMessage
should be the right way to get the message sent. Also, I wonder if the :Blur and :Focus messages should be moved to the browser.xml code?
Assignee | ||
Comment 3•14 years ago
|
||
Mhm, yes. I thought i tested it the upper way, but you are right... Might that i just changed it on device and didn't update my version working :)
I dont have a big feeling for one place or the other, so what ever works best - i would say :)
Updated•14 years ago
|
tracking-fennec: --- → ?
Assignee | ||
Comment 4•14 years ago
|
||
Fixed the comment. I thought about moving it to the xml, but i think its more obvious here. So i kept it in this place.
Attachment #472334 -
Attachment is obsolete: true
Attachment #476759 -
Flags: review?(mark.finkle)
Attachment #472334 -
Flags: review?(mark.finkle)
Assignee | ||
Updated•14 years ago
|
Assignee: nobody → jeremias.bosch
Status: NEW → ASSIGNED
Updated•14 years ago
|
tracking-fennec: ? → 2.0b2+
Assignee | ||
Comment 5•14 years ago
|
||
Its not that big patch, can we get it reviewed (+) :) soon?
Comment 6•14 years ago
|
||
Comment on attachment 476759 [details] [diff] [review]
Version 2
>diff --git a/chrome/content/browser.js b/chrome/content/browser.js
> let browsers = document.getElementById("browsers");
> browsers.addEventListener("command", this._handleContentCommand, true);
> browsers.addEventListener("DOMUpdatePageReport", gPopupBlockerObserver.onUpdatePageReport, false);
>+ browsers.addEventListener("focus", function() {
>+ Browser.selectedBrowser.messageManager.messageManager.sendAsyncMessage("Browser:Focus",{});
>+ }, true);
>+ browsers.addEventListener("blur", function() {
>+ Browser.selectedBrowser.messageManager.messageManager.sendAsyncMessage("Browser:Blur",{});
>+ }, true);
I want to move these handlers, and _handleContentCommand, into a Browser.handleEvent method. It seems like clutter here. Someone should do that on checkin.
checkin after beta 1
Attachment #476759 -
Flags: review?(mark.finkle) → review+
Updated•14 years ago
|
Whiteboard: [fennec-checkin-postb1]
Comment 7•14 years ago
|
||
I am worried about his patch. It is basically the same as bug 599053, which had problems too.
Whiteboard: [fennec-checkin-postb1]
Comment 8•14 years ago
|
||
I don't want to take this for b2. It could cause the same performance problems we saw in the original patch in bug 599053. (https://bugzilla.mozilla.org/attachment.cgi?id=478406&action=edit)
tracking-fennec: 2.0b2+ → 2.0+
Comment 9•14 years ago
|
||
Comment on attachment 476759 [details] [diff] [review]
Version 2
This has already landed
Attachment #476759 -
Flags: review+
Comment 10•14 years ago
|
||
Is there anything left to do here? Do we need this?
Assignee | ||
Comment 11•14 years ago
|
||
Yes we need this for meego handset, it was removed somewhen last year. will add updated patch today and add it to meego meta bug.
Comment 12•14 years ago
|
||
Comment on attachment 476759 [details] [diff] [review]
Version 2
bitrotted
Attachment #476759 -
Attachment is obsolete: true
Comment 15•14 years ago
|
||
Not sure we need this anymore
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
Updated•13 years ago
|
Attachment #505890 -
Flags: review?(mark.finkle)
You need to log in
before you can comment on or make changes to this bug.
Description
•