Bug #100909
closed
SvgTree.js // Page tree error
0%
Description
Link Browser
Steps to reproduce
1. Open then Link Browser, set a link
2. Navigate to the "page" Tab and wait until the JS starts to load the page broswer and immediately...
3. Switch to the "external url" Tab
4. "Page tree error" appears. (pagetree_networkErrorTitle / pagetree_networkErrorDesc)
5. Firefox shows NS_BINDING_ABORTED
The error always appears when the Tab will be switched from "page" to "external url".
AND when the loading of the page tree is interrupted by the user by changing the tab.
Files
Updated by Benni Mack over 1 year ago
- Sprint Focus changed from Stabilization Sprint to On Location Sprint
Updated by Riccardo De Contardi about 1 year ago
I am not able to reproduce it on 11.5.30 with Firefox. I slowed down the net to "Common 2G" to make sure to click on the "External URL" tab while the tree was still loading.
Same with Chrome (slowed down to "Slow 3G")
Do you have some further detail about how to reproduce it?
Updated by Ralph Brugger about 1 year ago
I think the problem does not depend on the internet speed but the speed of the pagetree loading.
I've made a screen recording video:
https://www.youtube.com/watch?v=uYH8L5HemCA
1. Open then Link Browser, set a link
2. Navigate to the "page" Tab and wait until the JS starts to load the page broswer and immediately...
3. Switch to the "external url" Tab
4. "Page tree error" appears. (pagetree_networkErrorTitle / pagetree_networkErrorDesc)
Updated by Benni Mack 5 months ago
- Status changed from New to Needs Feedback
Hey @Riccardo De Contardi how to continue here?
Updated by Riccardo De Contardi 5 months ago
@Ralph Brugger on version 13 the pagetree has been reworked; is this issue still true?
I confess that I actually don't know how to reproduce it.
Updated by Riccardo De Contardi 20 days ago
- Status changed from Needs Feedback to Closed
I think that this can be safely closed due to the new v.13 reworked pageTree and lack of feedback for the last 4 months
Digging into an issue like this for legacy trees won't likely happen
If you think that this is the wrong decision or experience the issue again on v.13 please reopen it or ping me and I'll happily do it
Thank you