Last modified: 2013-10-18 22:01:52 UTC
Could we have a way to bypass the browser blacklist. e.g. 1. a user preference to ignore the blacklist during initialisation, or 2. ?debug=true bypasses blacklist, 3. a test-wiki where the blacklist is empty/ignored, or 4. a simple way to re-run VE init from JS console This will allow mere mortals to help identify bugs with unsupported browsers. For option four, we can modify the blacklist, like so: JS> delete mw.libs.ve.blacklist.opera; But im not sure what to do after that.
For anyone wanting to bypass it on browser with a decent JS debugger, set a breakpoint on the line 'mw.libs.ve = init' in https://bits.wikimedia.org/static-1.22wmf10/extensions/VisualEditor/modules/ve-mw/init/targets/ve.init.mw.ViewPageTarget.init.js Then execute JS> delete init.blacklist.opera And resume running the VE scripts. Im guessing this isnt possible on most mobile browsers, so one of option 1-3 or similar would be useful.
You can already bypass the blacklist by using ?vewhitelist=1 - sorry, we should document this somewhere!
The code for this enhancement request had already been written before the bug rasied, but wasn't deployed at that time. https://gerrit.wikimedia.org/r/#/c/74574/ Changing from INVALID to FIXED, but maybe it is a dup of another bug?
