Last modified: 2014-06-09 22:06:37 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 T55456, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 53456 - Point to VE edit button in the GettingStarted tour only after the button is enabled
Point to VE edit button in the GettingStarted tour only after the button is e...
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
GettingStarted (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Matthew Flaschen
:
Depends on: 53143
Blocks:
  Show dependency treegraph
 
Reported: 2013-08-28 05:55 UTC by Steven Walling
Modified: 2014-06-09 22:06 UTC (History)
5 users (show)

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


Attachments
What is looks like on enwiki now (298.25 KB, image/png)
2013-08-28 05:55 UTC, Steven Walling
Details

Description Steven Walling 2013-08-28 05:55:58 UTC
Created attachment 13187 [details]
What is looks like on enwiki now

Currently, GettingStarted's guided tour points to the Save button in VE immediately on page load. This conflicts with the introductory modal VE presents to users, and even when that is not present (it only shows once) the guider is pointing to a disabled button. We should delay loading the guider pointing to the Save button until after the user has made changes and the button is enabled.
Comment 1 Sam Smith 2014-02-24 21:17:28 UTC
Possible approach:

* Extend ve.ui.mw.Target class to fire the "sanityCheckComplete" hook
* Add an awaitHook (?) property to the guider step definition, which indicates that the step should be shown once the hook has been fired
* Add the property to the third step of the firsteditve tour with the value "sanityCheckComplete"
Comment 2 Matthew Flaschen 2014-02-25 08:34:54 UTC
It seems more direct to put a hook in updateToolbarSaveButtonState (maybe ve.saveButton.stateChanged to match ve.saveDialog.stateChanged).  Although sanityCheckComlplete calls updateToolbarSaveButtonState, I consider that more of an implementation detail.  

As far as awaitHook, we basically have two choices:
* Add it as a shouldSkip before doing the non-linear tour refactoring (similar to the VE hooks already there), further cluttering the main library.
* Have this depend on bug 53143, and implement something like https://www.mediawiki.org/wiki/Extension:GuidedTour/Refactoring_brainstorming . This is a decent chunk of work, but it's already in our sprint.  See the part about the listenFor proposal on the MediaWiki.org page.
Comment 3 Sam Smith 2014-02-25 12:20:07 UTC
(In reply to Matthew Flaschen from comment #2)
> As far as awaitHook, we basically have two choices:
> * Add it as a shouldSkip before doing the non-linear tour refactoring
> (similar to the VE hooks already there), further cluttering the main library.
> * Have this depend on bug 53143, and implement something like
> https://www.mediawiki.org/wiki/Extension:GuidedTour/
> Refactoring_brainstorming.

Given that this is normal priority, my vote is for the cleaner of the two: fix 53143 first and then return to this (#2).

> This is a decent chunk of work, but it's already
> in our sprint.  See the part about the listenFor proposal on the
> MediaWiki.org page.

We can always remove this from the current sprint, taking care to note that it is blocked on 53143.
Comment 4 Gerrit Notification Bot 2014-04-02 06:23:42 UTC
Change 123171 had a related patch set uploaded by Mattflaschen:
Update firsteditve

https://gerrit.wikimedia.org/r/123171
Comment 5 Gerrit Notification Bot 2014-06-09 21:26:01 UTC
Change 123171 merged by jenkins-bot:
Update firsteditve

https://gerrit.wikimedia.org/r/123171

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


Navigation
Links