Last modified: 2010-07-21 11:13:50 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 T25536, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 23536 - Specialchars booklet does not remember selected page
Specialchars booklet does not remember selected page
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
UsabilityInitiative (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Trevor Parscal
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-15 19:45 UTC by Derk-Jan Hartman
Modified: 2010-07-21 11:13 UTC (History)
3 users (show)

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


Attachments

Description Derk-Jan Hartman 2010-05-15 19:45:36 UTC
From the feedback page: "Firstly, if I am inserting, for example, IPA characters from the IPA toolbar, when I press the preview button and the page reloads the toolbar goes back to Latin diacritics, which is somewhat annoying. "

I note that with the new "integrated" preview, this might become obsolete again though.
Comment 1 Roan Kattouw 2010-05-15 19:47:53 UTC
Is this about charinsert or the special characters section in the edit toolbar? The latter uses a cookie to preserve state IIRC.
Comment 2 Derk-Jan Hartman 2010-05-15 19:54:25 UTC
This is about the toolbar one.
Comment 3 Roan Kattouw 2010-05-15 21:43:06 UTC
I believe there is a cookie to preserve the state of the specialchars booklet, but a recent change by me may have broken this. I'll look into it.
Comment 4 Roan Kattouw 2010-07-21 11:13:50 UTC
(In reply to comment #3)
> I believe there is a cookie to preserve the state of the specialchars booklet,
> but a recent change by me may have broken this. I'll look into it.
Turns out there was a cookie, but it wasn't getting read correctly when trying to restore the state. Fixed in r69673.

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


Navigation
Links