Closed
Bug 1437241
Opened 6 years ago
Closed 6 years ago
ReferenceError: Cu is not defined browser-sync.js:8:1 when open Show All Bookmarks
Categories
(Firefox :: Sync, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1437242
Tracking | Status | |
---|---|---|
firefox-esr52 | --- | unaffected |
firefox58 | --- | unaffected |
firefox59 | --- | affected |
People
(Reporter: magicp.jp, Unassigned)
References
Details
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0 ID:20180208193705 Steps to reproduce: 1. Launch 59b on Windows 2. Open Show All Bookmarks (Ctrl+Shift+B) Or... Menu bar > Bookmarks > Show All Bookmarks Library > Bookmarks > Show All Bookmarks Actual results: The following errors are logged in the browser console. I can reproduce on Windows and Ubuntu (without macOS). ReferenceError: Cu is not defined browser-sync.js:8:1 TypeError: gSync is undefined places.js:141:5 Expected results: No errors Regression range: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=7971d134b3a351c0d5c32ed2f6c24349a05a5fb6&tochange=0c7a34d13dc36c736eebd6e80aee00cb2d4d697d
Blocks: 1384856
Has Regression Range: --- → yes
Has STR: --- → yes
status-firefox58:
--- → unaffected
status-firefox59:
--- → affected
status-firefox-esr52:
--- → unaffected
Updated•6 years ago
|
Component: Bookmarks & History → Sync
Comment 1•6 years ago
|
||
I doubt this can still happen, considered Cu now is set in every chrome context.
Comment 2•6 years ago
|
||
I can't reproduce this with today's Nightly on Windows.
(In reply to Mark Hammond [:markh] from comment #2) > I can't reproduce this with today's Nightly on Windows. You should try this with 59b. Bug 1437242 with Nightly.
Comment 4•6 years ago
|
||
(In reply to magicp from comment #3) > (In reply to Mark Hammond [:markh] from comment #2) > > I can't reproduce this with today's Nightly on Windows. > > You should try this with 59b. Bug 1437242 with Nightly. I tried it with a local build of -central from ~5 hours ago. I suspect(/hope) both these bugs have the same underlying issue - I'll try again tomorrow. Thanks!
Comment 5•6 years ago
|
||
I'm sure this was fixed by bug 1437242
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•