Closed
Bug 1442467
Opened 7 years ago
Closed 7 years ago
About:sync page displays partial content
Categories
(Firefox :: Sync, defect)
Firefox
Sync
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: kkumari, Unassigned)
Details
Attachments
(3 files)
STR:
1. Launch old Fx profile(Bookmarks ~1400 on client)
2. Sync it to existing sync account (~70 bookmarks and about:sync addon)
observed: Partial display of about:sync page. Please see attachment.
Reporter | ||
Comment 1•7 years ago
|
||
Reporter | ||
Comment 2•7 years ago
|
||
This issue is reproducible with any Fx and sync profile.
Updated•7 years ago
|
Component: Extension Compatibility → Sync
Reporter | ||
Comment 3•7 years ago
|
||
Browser console shows:
*** aboutsync: not installing aboutsync extension into window of type devtools:webconsole bootstrap.js:27
*** aboutsync: starting up bootstrap.js:27
render() failed Invariant Violation: findComponentRoot(..., .3.1.1.2.1): Unable to find element. This probably means the DOM was unexpectedly mutated (e.g., by the browser), usually due to forgetting a <tbody> when using tables, nesting tags like <form>, <p>, or <a>, or using non-SVG elements in an <svg> parent. Try inspecting the child nodes of the element with React ID ``.
Stack trace:
invariant@chrome://aboutsync/content/react-0.14.7/build/react.js:18350:15
findComponentRoot@chrome://aboutsync/content/react-0.14.7/build/react.js:11360:47
findReactNodeByID@chrome://aboutsync/content/react-0.14.7/build/react.js:11275:12
getNode@chrome://aboutsync/content/react-0.14.7/build/react.js:10758:21
didPutListener@chrome://aboutsync/content/react-0.14.7/build/react.js:14778:18
putListener@chrome://aboutsync/content/react-0.14.7/build/react.js:2380:7
wrapper@chrome://aboutsync/content/react-0.14.7/build/react.js:12349:16
putListener@chrome://aboutsync/content/react-0.14.7/build/react.js:6458:3
notifyAll@chrome://aboutsync/content/react-0.14.7/build/react.js:869:9
close@chrome://aboutsync/content/react-0.14.7/build/react.js:12866:5
closeAll@chrome://aboutsync/content/react-0.14.7/build/react.js:15695:11
perform@chrome://aboutsync/content/react-0.14.7/build/react.js:15642:11
batchedMountComponentIntoNode@chrome://aboutsync/content/react-0.14.7/build/react.js:10878:3
perform@chrome://aboutsync/content/react-0.14.7/build/react.js:15629:13
batchedUpdates@chrome://aboutsync/content/react-0.14.7/build/react.js:8456:7
batchedUpdates@chrome://aboutsync/content/react-0.14.7/build/react.js:13702:3
_renderNewRootComponent@chrome://aboutsync/content/react-0.14.7/build/react.js:11072:5
wrapper@chrome://aboutsync/content/react-0.14.7/build/react.js:12349:16
_renderSubtreeIntoContainer@chrome://aboutsync/content/react-0.14.7/build/react.js:11146:21
render@chrome://aboutsync/content/react-0.14.7/build/react.js:11166:12
wrapper@chrome://aboutsync/content/react-0.14.7/build/react.js:12349:16
render/<@chrome://aboutsync/content/components.js:1063:23
promise callback*render@chrome://aboutsync/content/components.js:1038:3
main@chrome://aboutsync/content/components.js:1085:3
@chrome://aboutsync/content/components.js:1099:1
components.js:1066:19
Sync encountered an error - see about:sync-log for the log file.
Reporter | ||
Comment 4•7 years ago
|
||
Comment 5•7 years ago
|
||
Thom, I'm guessing your refactor will fix this?
Comment 6•7 years ago
|
||
Yes, I believe so.
Comment 7•7 years ago
|
||
This is now working in the most recent version.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•