New Tab: activity-stream.bundle.js and css/activity-stream.css re-added after Bug 2025793 removed them
Categories
(Firefox :: New Tab Page, defect, P1)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr140 | --- | unaffected |
| firefox-esr153 | --- | unaffected |
| firefox153 | --- | unaffected |
| firefox154 | --- | unaffected |
| firefox155 | --- | fixed |
People
(Reporter: nina-py, Assigned: nina-py)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
Bug 2025793 stopped committing the generated New Tab bundle/CSS artifacts, added them to .gitignore, and deleted activity-stream.bundle.js, vendor.bundle.js, css/activity-stream.css, and css/nova/activity-stream.css from the tree so the build generates them instead.
Two of those, browser/extensions/newtab/data/content/activity-stream.bundle.js and browser/extensions/newtab/css/activity-stream.css, were then re-added by Bug 2050954 Part 1 (D309610). They are tracked again despite being listed in .gitignore, so the committed copies and the build-generated ones are out of sync.
Remove the two re-added files with git rm so only the build-generated copies remain, matching Bug 2025793's intent.
| Assignee | ||
Comment 1•4 days ago
|
||
Bug 2025793 stopped committing the generated newtab bundle and CSS and added
them to .gitignore, but Bug 2050954 later re-added
data/content/activity-stream.bundle.js and css/activity-stream.css to the tree.
Remove them again so only the build-generated, packaged copies remain.
Comment 2•4 days ago
|
||
Set release status flags based on info from the regressing bug 2050954
Comment 4•3 days ago
|
||
| bugherder | ||
Description
•