2.39 KB, text/html
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; YComp 18.104.22.168) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031211 When page is initally displayed, a default selection is shown for a radio button. If you click something on the page twice, that causes the frame to be redrawn twice, for example opening and closing the help panel or closing and reopening a portfolio, then the radio button selection changes to the bottom button. The focus (little gray dotted line around the button) stays at the correct (top) button, but the selection changes to the bottom button. I observe this behavior in several pages which contain radio buttons. In another panel, if I use my mouse to select the top button, then open or close the help panel, the top button remains selected, but the focus moves to the bottom button. The difference in the behavior of the two pages may be related to the initial setting of the button when arriving at the page. Reproducible: Always Steps to Reproduce: 1. Render a page that contains radio buttons, with top button set initially 2. Click something else on the page twice that causes it to be redrawn, for example open and close the help panel. 3. Observer that the radio button setting has changed to the bottom button, but focus remains on the top button. Actual Results: The actual setting of the radio button when is the bottom button (wrong). Expected Results: Expect radio button setting to be retained when help panel is opened then closed. If there is a workaround to this problem that we can use while awaiting a permanent fix, that would be great.
This sounds suspiciously like bug 175289...could you please have a look there and see if it's what you're describing?
Created attachment 137316 [details] html for a page which illustrates radio button problem YOu probably can't load this because it has lots of references to other files, but maybe looking at will tell you if this problem is related to 175289.
I looked at 175289 - the behavior sounds similar, but I see this behavior on pages which do not contain tables, and on pages which do not contain tr /tr blocks. I've attached my html in case it might be helpful.
That doesn't help too much unfortunately, because the radiobuttons must be in one of the linked documents; they don't show up when I load the file you attached. Do you have access to the other files, and if so could you zip them all up and attach them?
Unfortunately I do not have access to all of the infrastructure that this panel uses. I thought it might just give you a clue as to whether or not it is a dup.
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/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.