Last modified: 2013-09-30 16:20:54 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T45193, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 43193 - VisualEditor: Firefox has issues using VE when cookies are disabled
VisualEditor: Firefox has issues using VE when cookies are disabled
Status: RESOLVED FIXED
Product: VisualEditor
Classification: Unclassified
MediaWiki integration (Other open bugs)
unspecified
All All
: Low minor
: VE-deploy-2013-08-15
Assigned To: Roan Kattouw
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-12-17 11:13 UTC by turb
Modified: 2013-09-30 16:20 UTC (History)
5 users (show)

See Also:
Web browser: Firefox
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description turb 2012-12-17 11:13:59 UTC
When cookies are disabled, VisualEditor loads indef. It would better to either 1) be able to use it without cookies (I suppose that's not possible) or 2) display an adequate error message.

Tested on Firefox 17.0.1 with Cookie Monster 1.1.0.
Comment 1 Roan Kattouw 2012-12-18 08:29:08 UTC
You can't have *all* cookies disabled, otherwise you wouldn't be able to log in and enable the VE preference. I'm guessing this might be a badtoken error (in which case I'm pretty sure we do actually show an error message, rather than load forever; and in which case you're probably also unable to edit through the regular UI), or it might be something entirely unrelated to cookies.

Can you confirm whether VE always fails to load with Cookie Monster and always loads successfully without Cookie Monster?
Comment 2 Roan Kattouw 2012-12-18 08:30:20 UTC
(In reply to comment #1)
> Can you confirm whether VE always fails to load with Cookie Monster and
> always
> loads successfully without Cookie Monster?
And could you also confirm that you're able to edit *as a logged-in user* using the regular non-visual editor?
Comment 3 turb 2012-12-18 08:59:44 UTC
(In reply to comment #2)
> (In reply to comment #1)
> > Can you confirm whether VE always fails to load with Cookie Monster and
> > always
> > loads successfully without Cookie Monster?
> And could you also confirm that you're able to edit *as a logged-in user*
> using
> the regular non-visual editor?

I forgot to mention I was testing on VisualEditor:Test in mediawiki.org, that was not whitelisted in Cookie Monster. When I did whitelisted it, the page reloaded and VE was now working.

I just removed again mediawiki.org from whitelist, and VE now loads without end.

VE do work for me in en.wikipedia.org (that is of course whitelisted). I don't know if anonymous users can contribute with cookies disabled (for the day it will be activated for them).
Comment 4 turb 2012-12-18 09:08:41 UTC
Note: after some tests, VE does work with Chrome and IE9, with totally disabled cookies.
Comment 5 Roan Kattouw 2013-01-08 18:54:34 UTC
(In reply to comment #3)
> (In reply to comment #2)
> > (In reply to comment #1)
> > > Can you confirm whether VE always fails to load with Cookie Monster and
> > > always
> > > loads successfully without Cookie Monster?
> > And could you also confirm that you're able to edit *as a logged-in user*
> > using
> > the regular non-visual editor?
> 
> I forgot to mention I was testing on VisualEditor:Test in mediawiki.org, that
> was not whitelisted in Cookie Monster. When I did whitelisted it, the page
> reloaded and VE was now working.
> 
> I just removed again mediawiki.org from whitelist, and VE now loads without
> end.
> 
Does normal editing (through the old, non-visual editor) work for you on mediawiki.org when not whitelisted?
Comment 6 turb 2013-01-10 15:26:43 UTC
(In reply to comment #5)
> Does normal editing (through the old, non-visual editor) work for you on
> mediawiki.org when not whitelisted?

Yes, it works.
Comment 7 Krinkle 2013-09-27 18:02:14 UTC
Afaik the bad token handling has been solved for the save process. The load process no longer requires a token.

Can you confirm this now works fine?
Comment 8 turb 2013-09-27 18:26:43 UTC
(In reply to comment #7)
> Afaik the bad token handling has been solved for the save process. The load
> process no longer requires a token.
> 
> Can you confirm this now works fine?

Yes, it does work fine now, even with Cookie Monster preventing cookies to be set.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links