Bug 24140 – REGRESSION: Safari input field value update via Javascript not rendered in UI

• Status: RESOLVED
• Resolution: DUPLICATE
• Component: Layout and Rendering

[Ben Gummer]

Summary: 
When a text field in Safari 4 has a zero-length value AND has a non zero-length placeholder value, the first attempt to update the value of such a field (using Javascript) is not rendered in the browser UI.

Steps to Reproduce:
1. Create an HTML file containing a text field element with a zero-length value, such as <input type="text" value="" placeholder="Placeholder" id="test">
2. Use Javascript to update the value of the text field element, such as document.getElementById('test').value = "Javascript assigned value";
3. Notice that when the Javascript is run, the text field element still displays it's placeholder, and not the new value assigned using Javascript.
4. Run the Javascript a second time (without reloading the page).
5. Notice that the expected value is shown upon the second execution of the Javascript.

Expected Results:
When the Javascript is run for the first time, it is expected that the text field element will display the value assigned via Javascript.

Actual Results:
When the Javascript is run for the first time, the text field element continues to display it's placeholder value, instead of the new actual value assigned via Javascript. Executing the Javascript a second time causes the value changes to be rendered as expected.

Regression:
This problem only occurs when a text field element's 'placeholder' attribute is set to a non-zero-length string, AND when the same text field element's 'value' attribute is set to a zero-length string.

This problem does not occur in Safari 3.

Notes:
I have uploaded a demo script to demonstrate the problem (see http://pastie.org/399137.txt)

[Ben Gummer]

Created attachment 27938 [details]
A test script to reproduce the problem

[Alexey Proskuryakov]

Confirmed using  a local build of r41181.

[Alexey Proskuryakov]

<rdar://problem/6674177>

[Alexey Proskuryakov]

Please cross-reference bugs when filing both here and in Radar.

*** This bug has been marked as a duplicate of 24508 ***