Using Firefox latest
The page was reloaded, because the character encoding declaration of the HTML document was not found when prescanning the first 1024 bytes of the file. The encoding declaration needs to be moved to be within the first 1024 bytes of the file.
project:36
JQMIGRATE: Logging is active
project-bundle.js:10335:2
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user鈥檚 experience. For more help http://xhr.spec.whatwg.org/
project-bundle.js:9594:5
Source map error: request failed with status 404
Resource URL: http://127.0.0.1:3333/project-bundle.js
Source Map URL: underscore-min.map
[Learn More]
XML Parsing Error: not well-formed
Location: http://127.0.0.1:3333/command/core/set-preference
Line Number 1, Column 1:
set-preference:1:1
Error: Script terminated by timeout at:
ListFacet.prototype._reSortChoices@http://127.0.0.1:3333/project-bundle.js:32528:3
ListFacet.prototype.updateState@http://127.0.0.1:3333/project-bundle.js:32518:5
BrowsingEngine.prototype.update/<@http://127.0.0.1:3333/project-bundle.js:31356:9
fire@http://127.0.0.1:3333/project-bundle.js:3121:10
fireWith@http://127.0.0.1:3333/project-bundle.js:3233:7
done@http://127.0.0.1:3333/project-bundle.js:9277:5
callback@http://127.0.0.1:3333/project-bundle.js:9687:8
Actually, upon waiting and waiting.. eventually I see another error...
allocation size overflow
project-bundle.js:32795:33
ListFacet.prototype._update
http://127.0.0.1:3333/project-bundle.js:32795:33
ListFacet.prototype.updateState
http://127.0.0.1:3333/project-bundle.js:32524:3
BrowsingEngine.prototype.update/<
http://127.0.0.1:3333/project-bundle.js:31356:9
fire
http://127.0.0.1:3333/project-bundle.js:3121:10
fireWith
http://127.0.0.1:3333/project-bundle.js:3233:7
done
http://127.0.0.1:3333/project-bundle.js:9277:5
callback
http://127.0.0.1:3333/project-bundle.js:9687:8
We know we don't deal with large facets very well already in #672
And this is because of how / what we are doing with Jquery to populate any List Facets.
This doesn't seem high priority to me since it's an attempt to push beyond recommend boundaries. One easy way to fix the "bug" would be to enforce a reasonable upper limit on the text facet choice count.
Oh wow, this issue is still around? Let's close it. This was a limit test in actuality that I documented as an issue so that we had the capture of the actual error component. This issue just needed a glance over by you, Jacky, or Antonin at the time and could have been closed as "Will not fix" long long ago.
So doing that now. So to catch up from your time away, you only have about 400+ more issues to review Tom! ;-) jk