Closed
Bug 241927
Opened 20 years ago
Closed 19 years ago
Update in other tab disturbs form input
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
EXPIRED
People
(Reporter: u20230201, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.4.2) Gecko/20040220 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 I have an application that uses several frames. One frame has a kind of status area that periodically refreshes itself, controlled by Javascript. In another frame there's a text input area. When I write a longer text into the input field while the other frame refreshes, input characters occasionally loose their position and end up right of the input cursor, causing them to be scrolled right along with entering more text. This effect does not occur with MS IE 6.0! Reproducible: Always Steps to Reproduce: 1. Enetr text in one input ares while another frame refreshes itself. Actual Results: Occasionally characters appear right from the input cursor. Expected Results: Characters should not move along with inputting text
Comment 1•20 years ago
|
||
Please attach a testcase to this bug using http://bugzilla.mozilla.org/attachment.cgi?bugid=241927&action=enter
Reporter | ||
Comment 2•20 years ago
|
||
I'm sorry, but it seems I was wrong: The application seems to use "server push" technology to update the frame, not a client-side Javascript timer. Unfortunately the software is proprietary, so I cannot really provide any code from it. Maybe if someone has some server-push code at hand, he or she could try to create a multi-frame document, where one frame is periodically refreshed while theres some input in a textarea inside another frame. If nobody can do it, I could try it myself, but I never wrote such code before.
Severity: major → normal
Summary: JavaScript-controlled update in other frame disturbs form input → Update in other frame disturbs form input
Reporter | ||
Comment 3•19 years ago
|
||
The bug is still current, even for Firefox. As it turned out the scenario is like follows: An application using frames and javascript is running in one tab, and I'm entering text to some input area of another tab in the same window. Then occasionally order of letters gets wild. usually one character is right from the cursor and is being shifted on while more text is eneterd. I cannot provide the source code, because it's in an embedded device, and it's using conditional Javascript depending in the browser and Java, too. When trying to "mirror" the server, it bails out very early. Anyway I can tell you the following: The pages use "<meta http-equiv="Pragma" CONTENT="no-cache"> and Javascript do do things like this: function status() { ... setTimeout("status()", 500); ... }
Summary: Update in other frame disturbs form input → Update in other tab disturbs form input
Comment 4•19 years ago
|
||
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/
Comment 5•19 years ago
|
||
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
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•