Closed Bug 1070768 Opened 9 years ago Closed 9 years ago

Deal with fallout from bug 1050449

Categories

(SeaMonkey :: Autocomplete, defect)

defect
Not set
major

Tracking

(firefox34 fixed, firefox35 fixed, firefox36 fixed, seamonkey2.31 fixed, seamonkey2.32 fixed, seamonkey2.33 fixed)

RESOLVED FIXED
seamonkey2.33
Tracking Status
firefox34 --- fixed
firefox35 --- fixed
firefox36 --- fixed
seamonkey2.31 --- fixed
seamonkey2.32 --- fixed
seamonkey2.33 --- fixed

People

(Reporter: neil, Assigned: neil)

References

Details

Attachments

(2 files)

Bug 1050449 (landed last cycle) introduce a new toolkit file, toolkit/content/autocomplete.css which gets installed into chrome://global/content/autocomplete.css

However XPFE autocomplete also has an autocomplete.css which gets installed into chrome://global/content/autocomplete.css

Which one gets installed may depend on such factors as which -j value you use, whether you cloned a fresh mozilla-central or updated one from before bug 1050449, or which OS you use.

This is obviously an unhappy state of affairs and we should do something about it. In particular it might block us moving XPFE autocomplete from m-c into suite.

Since Thunderbird has stopped using XPFE autocomplete, we don't have to fight with them and Firefox as to how to proceed here which is a relief.

At the very least I propose we move XPFE autocomplete's content autocomplete.css from global to communicator. We can do this NPOTFB so that it can be uplifted to m-a.

There are a number of additional options but they would probably deserve separate bugs:
a) Moving XPFE autocomplete's skin autocomplete from global to communicator (although the communicator file would simply @import the global file needed for toolkit autocomplete).
b) Moving XPFE autocomplete's XBL binding from global to communicator
c) Moving XPFE autocomplete from m-c to suite
d) Binding XPFE autocomplete in communicator.css instead of xul.css
Flags: needinfo?(philip.chee)
Flags: needinfo?(iann_bugzilla)
> At the very least I propose we move XPFE autocomplete's content
> autocomplete.css from global to communicator. We can do this NPOTFB so that
> it can be uplifted to m-a.
Agreed.

> There are a number of additional options but they would probably deserve
> separate bugs:

> a) Moving XPFE autocomplete's skin autocomplete from global to communicator
> (although the communicator file would simply @import the global file needed
> for toolkit autocomplete).
We should remember to move modern at the same time.

> b) Moving XPFE autocomplete's XBL binding from global to communicator
> c) Moving XPFE autocomplete from m-c to suite
Once we move content css, skin css, and the XBL binding, what's left?

> d) Binding XPFE autocomplete in communicator.css instead of xul.css
Sure.
Flags: needinfo?(philip.chee)
Attached patch Proposed patchSplinter Review
OK, so this does step 1 which suffices to unbreak us.
Assignee: nobody → neil
Status: NEW → ASSIGNED
Attachment #8501985 - Flags: review?(philip.chee)
Attachment #8501985 - Flags: review?(philip.chee) → review+
Blocks: 492444
https://hg.mozilla.org/mozilla-central/rev/93802d266a82
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → seamonkey2.33
Comment on attachment 8501985 [details] [diff] [review]
Proposed patch

Approval Request Comment
[Feature/regressing bug #]: 1050449
[User impact if declined]: SeaMonkey autocomplete is broken
[Describe test coverage new/current, TBPL]: N/A
[Risks and why]: Not part of Firefox
[String/UUID change made/needed]: None
Attachment #8501985 - Flags: approval-mozilla-beta?
Attachment #8501985 - Flags: approval-mozilla-aurora?
Comment on attachment 8501985 [details] [diff] [review]
Proposed patch

Given that this will not impact Firefox, I'm approving based on the fact that there is a request for SeaMonkey.
Attachment #8501985 - Flags: approval-mozilla-beta?
Attachment #8501985 - Flags: approval-mozilla-beta+
Attachment #8501985 - Flags: approval-mozilla-aurora?
Attachment #8501985 - Flags: approval-mozilla-aurora+
Oops, fix was incomplete.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Attached patch Additional patchSplinter Review
Attachment #8518051 - Flags: review?(philip.chee)
Comment on attachment 8518051 [details] [diff] [review]
Additional patch

r=me WFM
Attachment #8518051 - Flags: review?(philip.chee) → review+
Comment on attachment 8518051 [details] [diff] [review]
Additional patch

Approval Request Comment
[Feature/regressing bug #]: 1050449
[User impact if declined]: SeaMonkey autocomplete is still broken
[Describe test coverage new/current, TBPL]: N/A
[Risks and why]: Not part of Firefox
[String/UUID change made/needed]: None
Attachment #8518051 - Flags: approval-mozilla-beta?
Attachment #8518051 - Flags: approval-mozilla-aurora?
https://hg.mozilla.org/mozilla-central/rev/ac8de9bcd5d6
Status: REOPENED → RESOLVED
Closed: 9 years ago9 years ago
Resolution: --- → FIXED
Comment on attachment 8518051 [details] [diff] [review]
Additional patch

Beta+
Aurora+
Attachment #8518051 - Flags: approval-mozilla-beta?
Attachment #8518051 - Flags: approval-mozilla-beta+
Attachment #8518051 - Flags: approval-mozilla-aurora?
Attachment #8518051 - Flags: approval-mozilla-aurora+
Flags: needinfo?(iann_bugzilla)
Pushed by frgrahl@gmx.net:
https://hg.mozilla.org/comm-central/rev/9d89b054b860
Move XPFE's autocomplete.css to communicator so it doesn't conflict with toolkit's new global autocomplete.css r=Ratty
https://hg.mozilla.org/comm-central/rev/83e7581a608f
Fix up more references to XPFE's autocomplete.css r=Ratty
You need to log in before you can comment on or make changes to this bug.