My favorites | Sign in
Project Home Downloads Wiki Issues Code Search
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 52845: wrong rendered input type=number element
4 people starred this issue and may be notified of changes. Back to list
Status:  Fixed
Owner:  tkent@chromium.org
Closed:  Feb 2011
Cc:  dglazkov@chromium.org

Restricted
  • Only users with EditIssue permission may comment.


Sign in to add a comment
 
Reported by lukasz.w...@magari-internet.de, Aug 20, 2010
Chrome Version       : 7.0.501.0 (56851)
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
     Safari 4: -
  Firefox 3.x: -
         IE 7: -
         IE 8: -

What steps will reproduce the problem?
1.
2.
3.

What is the expected result?
properly rendered input type=number element with up and down arrows

What happens instead?
rendering turns up button black and down button white

Please provide any additional information below. Attach a screenshot if
possible.

source.txt
24.3 KB   View   Download
screen.png
78.0 KB   View   Download
Aug 20, 2010
#1 tkent@chromium.org
Could you tell us what OS/distribution you used please?

Cc: tk...@chromium.org
Aug 20, 2010
#2 stuartmorgan@chromium.org
(No comment was entered for this change.)
Labels: -Area-Undefined Area-WebKit
Aug 23, 2010
#3 lukasz.w...@magari-internet.de
my OS is: MS Windows XP Professional Version 2002 Service Pack 3
Aug 23, 2010
#4 lukasz.w...@magari-internet.de
here I have attached another source file. You will see there that this bug happens when the inputs' parent element is set to overlow:hidden and has a border radius.
min.txt
662 bytes   View   Download
number-bug.png
459 bytes   View   Download
Sep 9, 2010
#5 ka...@chromium.org
(No comment was entered for this change.)
Cc: dglaz...@chromium.org
Labels: Mstone-X
Jan 20, 2011
#6 tkent@chromium.org
 Issue 64175  has been merged into this issue.
Jan 20, 2011
#7 tkent@chromium.org
Confirmed with 10.0.642.0 canary Windows 7.
Not reproducible on Mac.

 Issue 70061  looks a similar issue though it is triggered by "opacity".

Status: Available
Labels: OS-Windows
Feb 14, 2011
#8 tkent@chromium.org
 Issue 70061  has been merged into this issue.
Feb 14, 2011
#9 tkent@chromium.org
I posted a patch to WebKit: https://bugs.webkit.org/show_bug.cgi?id=54427

Status: Started
Owner: tk...@chromium.org
Cc: -tk...@chromium.org
Feb 15, 2011
#10 tkent@chromium.org
Fixed by http://trac.webkit.org/changeset/78677

Status: Fixed
Labels: -Mstone-X Mstone-11
Oct 12, 2012
#11 bugdro...@chromium.org
This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.
Labels: Restrict-AddIssueComment-Commit
Mar 10, 2013
#12 bugdro...@chromium.org
(No comment was entered for this change.)
Labels: -Area-WebKit -Mstone-11 M-11 Cr-Content
Mar 13, 2013
#13 bugdro...@chromium.org
(No comment was entered for this change.)
Labels: -Restrict-AddIssueComment-Commit Restrict-AddIssueComment-EditIssue
Apr 5, 2013
#14 bugdro...@chromium.org
(No comment was entered for this change.)
Labels: -Cr-Content Cr-Blink
Sign in to add a comment

Powered by Google Project Hosting