New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 590477 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner:
Last visit 29 days ago
Closed: May 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug



Sign in to add a comment

Style pane numeric property change modifier shortcuts are undiscoverable. Shift mousewheel doesn't work

Reported by noj...@gmail.com, Feb 27 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.0 Safari/537.36

Steps to reproduce the problem:
1. Go to google.com
2. Select #sfdiv
3. Select max-width
4. Mousewheel on max-width changes it
5. Shift mousewheel does nothing. Shift up/down adds +-10. Alt and pg/up down are totally undiscoverable for +-0.1 and +-100 modifiers

What is the expected behavior?
Shift + mousewheel / up / down should change numeric property by 10
alt + .. should change .. by 0.1
ctrl + .. should change .. by 100

What went wrong?
While testing css changes, especially font-size, margin, padding, translate, opacity and other numeric properties having precision modifiers would make it a lot easier to get a number in human brain translated to a css property value.

Did this work before? No 

Chrome version: 50.0.2661.0  Channel: n/a
OS Version: 10.0
Flash Version: Shockwave Flash 21.0 r0

I have a working fix for this. Turns out shift+mousewheel sends as deltaX rather than deltaY. I also added ctrl as +- 100 modifier. There is page up/down but those keys aren't very usable due to their location in the keyboard.

I have also added a tooltip that shows up when doing such modifications to increase discover-ability. 

Let me know what you think?, will send a patch by EOD for review.
 
mousewheel fix.png
200 KB View Download

Comment 1 by caseq@chromium.org, Mar 14 2016

Components: -Platform>DevTools Platform>DevTools>UX Platform>DevTools>HTML
Labels: -OS-Windows -Pri-2 -Arch-x86_64 OS-All Pri-3
Owner: lushnikov@chromium.org
Status: Assigned (was: Unconfirmed)

Comment 3 by noj...@gmail.com, May 9 2016

Doesn't the commit automatically close the bug? Or does someone have to go and close it?
Status: Fixed (was: Assigned)
This is fixed now.

Comment 5 by noj...@gmail.com, May 9 2016

Perfect. I'm glad this is in. My designer friends probably owe me a beer now. 

Sign in to add a comment