Last modified: 2014-10-20 15:43:34 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 T73732, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 71732 - VisualEditor: [Regression?] Save button stays disabled after inserting a character in some cases
VisualEditor: [Regression?] Save button stays disabled after inserting a char...
Status: RESOLVED FIXED
Product: VisualEditor
Classification: Unclassified
Data Model (Other open bugs)
unspecified
All All
: High major
: VE-deploy-2014-10-16
Assigned To: Roan Kattouw
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2014-10-07 04:15 UTC by Krinkle
Modified: 2014-10-20 15:43 UTC (History)
6 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Krinkle 2014-10-07 04:15:07 UTC 
1. Open https://www.mediawiki.org/wiki/QA/Selenium_Workshop in latest stable Chrome.
2. Click "Edit"
3. Put cursor in the first paragraph, insert a single character.

Expected:

Save button enables, allowing the user to save the page.

Actual:

Save button stays disable, user is unable to save the edit.

No exceptions or warnings on the dev console.
Comment 1 Krinkle 2014-10-07 04:16:36 UTC 
It seems the model is consistently one character behind. When I worked-round the bug in comment #0 by backspacing over my new character and typing it again, and then changing another word on the page, clicking Save page and reviewing my change showed only the first word change in the wikitext diff.
Comment 2 Roan Kattouw 2014-10-07 07:41:58 UTC 
Could this be fixed by https://gerrit.wikimedia.org/r/164514 ?
Comment 3 James Forrester 2014-10-07 15:55:01 UTC 
This works fine if the first cursor position is in the Header, or before the first character of the paragraph. Very complex behaviour…
Comment 4 Ed Sanders 2014-10-07 15:57:56 UTC 
Works for me in latest Chrome
Comment 5 Ed Sanders 2014-10-07 16:03:49 UTC 
Only happens on first click.
Comment 6 James Forrester 2014-10-20 15:43:34 UTC 
This appears to now be fixed in wmf3.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links