Last modified: 2013-06-26 01:40:00 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 T35113, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 33113 - VisualEditor: Have buttons that are greyed out disabled completely (UI effects still trigger)
VisualEditor: Have buttons that are greyed out disabled completely (UI effect...
Status: RESOLVED FIXED
Product: VisualEditor
Classification: Unclassified
Editing Tools (Other open bugs)
unspecified
All All
: Normal minor
: VE-deploy-2013-06-27
Assigned To: Rob Moen
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-12-14 16:14 UTC by Liangent
Modified: 2013-06-26 01:40 UTC (History)
9 users (show)

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


Attachments
Patch fixing it (470 bytes, patch)
2011-12-17 21:13 UTC, joan.creus.c
Details

Description Liangent 2011-12-14 16:14:05 UTC
Currently hover your mouse cursor over a disabled button there's still visual effect.
Comment 1 joan.creus.c 2011-12-17 21:13:10 UTC
Created attachment 9731 [details]
Patch fixing it

(I am new to this project and I do not know how it works much.)

To see how it worked, I decided to try to fix a bug. I am sending the svn diff resulting text. It works for me, tested on Firefox 8 and since it's standard CSS it should work everywhere.

I have tried to follow the coding style in the file, however, I do not know if I've done it OK.

It basically adds a :hover event to the disabled buttons, which sets the border to transparent with !important to override the border-color set by the other :hover event.
Comment 2 joan.creus.c 2011-12-17 21:18:27 UTC
By the way, I do not know if cursor should be set to normal when hovering. (I believe) now when hovering over normal buttons sets it to pointer; I do not know if this is considered "visual effect". In any case, it would be adding cursor:default !important; after the line I added.
Comment 3 Mark A. Hershberger 2011-12-17 23:58:56 UTC
r106536
Comment 4 Mark A. Hershberger 2011-12-29 21:17:51 UTC
Krinkle says:

  Why the !important rule ? The need for that rule is very rare I don't think
  this is one of those cases. CSS cascades the rules down later rules overwrite
  earlier ones.

  Since this rule has the same "score" (or "weight") as the :hover rule for
  normal buttons, this should work just fine.

  .es-toolbarButtonTool:hover,
  .es-toolbarDropdownTool:hover {
	border-color: #eeeeee;
  } 

  .es-toolbarButtonTool-disabled:hover {
	border-color: transparent;
  }

I'll apply this unless you object for some reason.
Comment 5 joan.creus.c 2011-12-29 21:32:42 UTC
You're right. No problem. It was just as a double measure of safety.

Thanks for spotting this, and sorry.
Comment 6 Krinkle 2011-12-30 02:16:02 UTC
(In reply to comment #5)
> You're right. No problem. It was just as a double measure of safety.
> 
> Thanks for spotting this, and sorry.

Don't worry. Better safe then sorry, this one was just a little too safe :)
Comment 7 Krinkle 2012-01-08 00:26:48 UTC
Applied by Mark in r108056. Fixed.
Comment 8 James Forrester 2012-10-15 22:57:47 UTC
Mass-moving old VisualEditor tickets to the VE product. Search for this message to mass-delete bugmail.
Comment 9 James Forrester 2012-10-29 18:10:09 UTC
Noting bugs closed in the 2012-10-15 release.
Comment 10 This, that and the other (TTO) 2013-06-24 04:57:55 UTC
(In reply to comment #0)
> Currently hover your mouse cursor over a disabled button there's still visual
> effect.

This effect has come back. In addition, the "pointer" cursor is used for disabled buttons, which seems wrong.
Comment 11 Gerrit Notification Bot 2013-06-24 19:04:58 UTC
Related URL: https://gerrit.wikimedia.org/r/70231 (Gerrit Change Icbf9ac6cff5e3f914268fe14d1b430609dedd49e)
Comment 12 James Forrester 2013-06-26 01:40:00 UTC
Fixed in above commit and will go out in a few minutes.

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


Navigation
Links