Closed
Bug 236644
Opened 21 years ago
Closed 21 years ago
Element's attribute has a cloon?
Categories
(Other Applications :: DOM Inspector, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: maye, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040207 Firefox/0.8
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040207 Firefox/0.8
I made a simpe HTML page:
<html><body><form><input type="text" value="abc"></form></body></html>
Then I open DOM Instector, locate to that input, you can find it's value is
"abc", If you edit it, it will show in webpage, then, I type something in web
browser directly, DOM inspector will not update the value, it's OK, but if I
edit the value in DOM inspector again, It did not show the change in the web
browser.
So I make a little more complex page, I found
Element.value!=Element.getAttribute("value")
and web browser always show Element.value, and I always can't touch it via way
like DOMWindow -> DOMDocument -> DOMElement -> Attribue, I think it's a bug,
otherwise there should be a way to access it.
Reproducible: Always
Steps to Reproduce:
![]() |
||
Comment 1•21 years ago
|
||
> Element.value!=Element.getAttribute("value")
That's correct. Element.defaultValue == Element.getAttribute("value"), but
Element.value is a totally separate beast.
So what is this bug about? Being able to set element.value in Inspector? Or what?
OK, but if Element.defaultValue == Element.getAttribute("value"),then how can I
touch the Element.Valye at run time, I am not mean with JavaScript, I mean using
Native windows (Embed gtk or Embed win) to access DOM Element. For example, If I
change input in form, How can I get it from Native windows, not from JS? Thanks
![]() |
||
Comment 3•21 years ago
|
||
You QI it to whatever interface has the .value property and get it (eg QI to
nsIDOMHTMLInuptElement and call GetValue()/SetValue() as needed.
Please ask such "how do I" questions in the right place (the newsgroups), not in
the bug database...
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → INVALID
Thanks, Sorry about wrong place, because I try it in DOM inspector, it can't
update neither, so I think it maybe a bug
Updated•20 years ago
|
Product: Core → Other Applications
Updated•18 years ago
|
Assignee: dom-inspector → nobody
QA Contact: timeless → dom-inspector
You need to log in
before you can comment on or make changes to this bug.
Description
•