The default bug view has changed. See this FAQ.

Remove useless "container" div from about:home

RESOLVED FIXED in Firefox 13

Status

()

Firefox
General
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: dao, Assigned: dao)

Tracking

Trunk
Firefox 14
Points:
---

Firefox Tracking Flags

(firefox13 fixed)

Details

(Whiteboard: [qa-])

Attachments

(1 attachment)

(Assignee)

Description

5 years ago
Created attachment 606971 [details] [diff] [review]
patch
Attachment #606971 - Flags: review?(mak77)

Updated

5 years ago
Attachment #606971 - Flags: review?(mak77) → review+
(Assignee)

Comment 1

5 years ago
http://hg.mozilla.org/integration/mozilla-inbound/rev/70cdb996d790
Target Milestone: --- → Firefox 14
I think once it is merged, may be worth to have this in Aurora, since snippets are going to be rewritten better to give them stable document contents (yes, wouldn't be hard to workaround this, but no reason to not avoid that).
(Assignee)

Comment 3

5 years ago
> snippets are going to be rewritten better to give them stable document
> contents

What exactly does this mean with regards to this bug?
snippets can modify css, for example when they changed the background to black for a day in the past. They may try to do that on "container" and get different results across versions.
I actually forgot a comma in that phrase, "snippets are going to be rewritten, so better give them"
(Assignee)

Updated

5 years ago
Attachment #606971 - Flags: approval-mozilla-aurora?
https://hg.mozilla.org/mozilla-central/rev/70cdb996d790
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED

Comment 7

5 years ago
Comment on attachment 606971 [details] [diff] [review]
patch

[Triage Comment]
Low risk patch in support of correctness in a new feature. Approved for Aurora 13.
Attachment #606971 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
(Assignee)

Comment 8

5 years ago
http://hg.mozilla.org/releases/mozilla-aurora/rev/0cf845b2ede5
status-firefox13: --- → fixed
Whiteboard: [qa-]
You need to log in before you can comment on or make changes to this bug.