Closed
Bug 930535
Opened 11 years ago
Closed 11 years ago
enable image visibility on b2g inside browser elements
Categories
(Core :: Layout: Images, Video, and HTML Frames, defect)
Tracking
()
RESOLVED
FIXED
mozilla27
People
(Reporter: tnikkel, Assigned: tnikkel)
References
Details
Attachments
(1 file)
4.02 KB,
patch
|
MatsPalmgren_bugz
:
review+
khuey
:
review+
|
Details | Diff | Splinter Review |
The first step to enabling on b2g is to enable it inside browser elements on b2g, as opposed to apps and the system. This should be the most similar to the Fennec and desktop situation where we don't have things like system or apps.
Attachment #821682 -
Flags: review?(matspal)
Assignee | ||
Updated•11 years ago
|
Attachment #821682 -
Flags: review?(khuey)
Assignee | ||
Comment 1•11 years ago
|
||
It should be noted that currently we do not lock images on b2g, but Lock/Unlock as called from image loading content still determines which images we call StartDecoding on (which is worse than RequestDecode).
Comment 2•11 years ago
|
||
Comment on attachment 821682 [details] [diff] [review] enabrowseronly >+ if (docshell && !docshell->GetIsInBrowserElement()) { >+ return true; I'd slightly prefer "if (!docshell || ..." because we return true for other error cases earlier.
Attachment #821682 -
Flags: review?(matspal) → review+
Assignee | ||
Comment 3•11 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/a32f9f36d344
Attachment #821682 -
Flags: review?(khuey) → review+
Comment 4•11 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/a32f9f36d344
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla27
Updated•6 years ago
|
Product: Core → Core Graveyard
Updated•6 years ago
|
Product: Core Graveyard → Core
You need to log in
before you can comment on or make changes to this bug.
Description
•