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

Issue 56226 link

Starred by 24 users

Issue metadata

Status: Fixed
Owner:
Closed: Oct 2010
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression
M-8

Restricted
  • Only users with EditIssue permission may comment.



Sign in to add a comment

REGRESSION: Placeholder attribute won't clear after second focus

Reported by seddon.r...@gmail.com, Sep 20 2010

Issue description

Chrome Version       : 7.0.524.0 canary build
URLs (if applicable) : http://www.thecssninja.com/demo/placeholder_issue/
Other browsers tested: Safari 5, Firefox 4 beta 6, Chrome 6
Add OK or FAIL after other browsers where you have tested this issue:
     Safari 4: OK
  Firefox 3.x: N/A
         IE 7: N/A
         IE 8: N/A

What steps will reproduce the problem?
1. Bring focus to a input field with the placeholder attribute
2. Remove focus
3. Bring back focus to field

What is the expected result?
Placeholder text should disappear and if the field is empty re-appear on blur

What happens instead?
The initial focus clears the hint and blurring brings it back, re-focusing doesn't remove it and instead treats the placeholder an entered value and never clears it again. This only happens on inputs, teaxtarea works as expected.

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

 
Labels: -Area-Undefined Area-WebKit WebKit-WebApps
Looks like a webkit issue.  

Bug filed upstream
https://bugs.webkit.org/show_bug.cgi?id=45940

Regression occurred early last week.

Comment 2 by karen@chromium.org, Sep 23 2010

Labels: Mstone-8 Regression

Comment 3 by kerz@chromium.org, Oct 1 2010

 Issue 57483  has been merged into this issue.

Comment 4 by dhw@chromium.org, Oct 5 2010

 Issue 57751  has been merged into this issue.

Comment 5 by dhw@chromium.org, Oct 5 2010

Status: Available
Summary: REGRESSION: Placeholder attribute won't clear after second focus

Comment 6 by tkent@chromium.org, Oct 6 2010

 Issue 57816  has been merged into this issue.

Comment 7 by tkent@chromium.org, Oct 6 2010

Status: Started
The patch in webkit.org/b/45940 will fix this.

 Issue 58060  has been merged into this issue.
 Issue 57710  has been merged into this issue.
 Issue 57735  has been merged into this issue.
 Issue 58043  has been merged into this issue.
Status: Fixed
This was fixed by WebKit r69176 and Chromium r61700.

Comment 13 by dhw@chromium.org, Oct 8 2010

 Issue 58436  has been merged into this issue.
 Issue 58573  has been merged into this issue.
 Issue 58617  has been merged into this issue.
 Issue 58718  has been merged into this issue.
 Issue 58967  has been merged into this issue.
Labels: -Regression bulkmove Type-Regression
Project Member

Comment 19 by bugdroid1@chromium.org, Oct 13 2012

Labels: Restrict-AddIssueComment-Commit
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.
Project Member

Comment 20 by bugdroid1@chromium.org, Mar 9 2013

Labels: -Area-WebKit -WebKit-WebApps -Mstone-8 -Type-Regression Cr-Content Type-Bug-Regression M-8 Cr-Content-WebApps
Project Member

Comment 21 by bugdroid1@chromium.org, Mar 13 2013

Labels: -Restrict-AddIssueComment-Commit Restrict-AddIssueComment-EditIssue
Project Member

Comment 22 by bugdroid1@chromium.org, Apr 6 2013

Labels: -Cr-Content Cr-Blink

Sign in to add a comment