Closed Bug 1014201 (ship-incontent-prefs) Opened 7 years ago Closed 6 years ago

Ship the in-content preferences

Categories

(Firefox :: Preferences, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: jaws, Unassigned)

References

(Depends on 1 open bug)

Details

(Keywords: addon-compat, meta)

No description provided.
Flags: firefox-backlog+
Depends on: 1014208
Depends on: 1014698
Alias: ship-incontent-prefs
Depends on: 1014758
Depends on: 989469
Depends on: 1017156
Depends on: 1017423
Depends on: 1017594
Depends on: 1017874
Depends on: 1017964
Depends on: 1018066
No longer depends on: 1017964
Depends on: 1016266
Depends on: 1018405
No longer depends on: 1019828
Depends on: 1020061
Depends on: 1020245
Depends on: 1020295
Depends on: 1020285
No longer depends on: 1020061
Depends on: 1025719
Depends on: 1028575
No longer depends on: 1016266
Depends on: 1021146
I talked with mmaslaney, jgruen, gavin, and dolske and we decided to not block shipping the in-content prefs until the add-ons manager styling has been updated.

The updated interactions and visual design of the in-content prefs are an incremental improvement and won't introduce any more visual inconsistencies within the product that aren't already present between {windows preferences, error pages, about: pages, add-ons manager, about:healthreport, about:home}.

There is potential that there may be small tweaks (such as consistent background colors) that can be done to other in-content pages to help bring the designs closer. A breakdown of the potential work there will need to happen.
No longer depends on: 989469, 1000625
Depends on: 1033674
Depends on: 1034296
Depends on: 1034362
Depends on: 1035211
Depends on: 1035308
Depends on: 1036434
Depends on: 1035625
Depends on: 1037081
Depends on: 1037225
Depends on: 1034999
Depends on: 1037859
No longer depends on: 993361
No longer depends on: 1008167
No longer depends on: 1008169
No longer depends on: 1020285
No longer depends on: 1022578
No longer depends on: 1022581
No longer depends on: 1024684
No longer depends on: 1037859
No longer depends on: 1034362
No longer depends on: 1041170
Depends on: 1042300
Depends on: 1043612
Depends on: 1044597
Depends on: 1044600
Depends on: 1047591
Depends on: 1047595
Depends on: 1047586
Depends on: 1043346
Depends on: 1055370
Depends on: 1055873
Depends on: 1055973
Depends on: 1062854
Depends on: 1046783
No longer depends on: 1046783
Depends on: 1064261
could 839441 be fixed to with this?
(In reply to Lars Gusowski [:lagu] from comment #2)
> could 839441 be fixed to with this?

https://bugzilla.mozilla.org/show_bug.cgi?id=839441
(In reply to Lars Gusowski [:lagu] from comment #3)
> (In reply to Lars Gusowski [:lagu] from comment #2)
> > could 839441 be fixed to with this?
> 
> https://bugzilla.mozilla.org/show_bug.cgi?id=839441

The goal of this bug (bug 1014201) is to fix only the most minimum set of bugs necessary to ship the new in-content-prefs. New enhancements can be fixed any time, but they will not be prioritized higher than the work that is blocking us from shipping our first version.
No longer depends on: 1050474
Depends on: 1083180
Depends on: 1083094
Depends on: 1090348
Depends on: 1091324
Depends on: 1013696
No longer depends on: 1013696
No longer depends on: 1014208
Depends on: 1012410
Depends on: 1022578
No longer depends on: 752197
Depends on: 1014208
No longer depends on: 1091324
No longer depends on: 1047595
No longer depends on: 1047591
No longer depends on: 1055341
No longer depends on: 1064261
No longer depends on: 1083094
No longer depends on: 1090348
No longer depends on: 1017494
No longer depends on: 1095017
No longer depends on: 1096779
Depends on: 1026679
No longer depends on: 1026679
Depends on: 1097543
No longer depends on: 1056478
Depends on: 1056478
Depends on: 1104076
Depends on: 1105254
No longer depends on: 1105254
Depends on: 1105545
Depends on: 1106240
Depends on: 1106241
No longer depends on: 1106241
Depends on: 1047591
No longer depends on: 1047591
Depends on: 1112294
Depends on: 1113197
Depends on: 1113173
Depends on: 991461
Depends on: 1114338
Depends on: 1115924
Depends on: 1115925
Depends on: 1116304
Depends on: 1022581
Depends on: 1119368
Depends on: 1119472
Depends on: 1108302
Depends on: 1111540
Depends on: 919526
Depends on: 1117557
Depends on: 1116584
Depends on: 1124483
Depends on: 1126278
No longer depends on: 1116304
No longer depends on: 1115924
No longer depends on: 1056478
No longer depends on: 1014208
No longer depends on: 919526
Depends on: 1127288
Depends on: 1128173
Depends on: 1128175
Depends on: 1128177
Depends on: 1128237
Depends on: 1129587
Depends on: 1129597
No longer depends on: 1129597
Depends on: 1129597
Depends on: 1129930
Depends on: 1129947
Depends on: 1130007
No longer depends on: 1129947
Depends on: 1130741
No longer depends on: 1116584
No longer depends on: 1130741
Depends on: 1133604
Depends on: 1135375
Depends on: 1036815
Depends on: 1136645
Depends on: 1064261
Depends on: 1141055
Depends on: 1142045
Depends on: 1141031
No longer depends on: 1064261
Depends on: 1148024
Depends on: 1148923
Depends on: 1149230
Depends on: 1151252
Shouldn't this be marked Fixed now that Firefox 38 shipped with in-content preferences?
Bug 1135375
https://www.mozilla.org/firefox/38.0/releasenotes/
Flags: needinfo?(jaws)
Yeah, we can close this. We still want to get the remaining dependencies fixed though.
Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(jaws)
Resolution: --- → FIXED
Blocks: 1145701
Depends on: 1194346
Depends on: 1194842
Depends on: 1502277
You need to log in before you can comment on or make changes to this bug.