Open Bug 277892 Opened 20 years ago Updated 2 years ago

values of some attributes are not correspond with values of propeties of textbox

Categories

(Core :: XUL, defect)

defect

Tracking

()

UNCONFIRMED

People

(Reporter: surkov, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3) Gecko/20040913 Firefox/0.10.1 (ax)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3) Gecko/20040913 Firefox/0.10.1 (ax)

Properties of textbox 'value', 'type', 'disabled', 'size', 'maxLength' 'readonly'
do not modify corresponding attributes (see comments 5-10 of
https://bugzilla.mozilla.org/show_bug.cgi?id=196148 bug).

Reproducible: Always

Steps to Reproduce:
OS: Windows 2000 → All
Hardware: PC → All
Before fixing this bug it's needed to fix
https://bugzilla.mozilla.org/show_bug.cgi?id=277899 bug.
like bug 277899, this is invalid. see explanation there.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
to asqueella: What do you think about it?
I'm not knowledgable enough to argue about it, but I would certainly like
toolkit code to be more consistent or at least to get a clear explanation of why
some properties update attributes and some don't. biesi, could you explain or
point us to a document explaining that?

If not, I think you should ask in a (npm.xul?) newsgroup. Please post here or
mail me if you get an answer on this issue.
no attribute is supposed to be updated when you change the properties. for which
attribute is that the case for you?
if you meant the other way round, then yes, the properties are supposed to be
updated when the attributes change, AIUI. the best newsgroup for this is
probably npm.dom (or maybe npd.xul)
Actually, what's supposed to happen here is just a matter of what's specified in
XUL.  In HTML, for example, some properties modify attributes, and some do not...

ccing Neil in case we have this written up somewhere.
Sorry, I'm not aware of any relevant documentation. I realize many properties
are mapped to attributes but that's probably just for reasons of convenience.
Ok. There is no complete xul specification (I mean
http://www.mozilla.org/projects/xul/xul.html). Should properties and attributes
be concerted? I see one reason to do it: it will be convenience.

Should this bug be reopened?
I'll reopen it since I was resolving under a wrong assumption; but it may still
be invalid (someone else will need to decide that)
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
still actual
Assignee: jag → nobody
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.