Closed Bug 125290 Opened 23 years ago Closed 23 years ago

0.9.8 pop up windows don't accept text

Categories

(SeaMonkey :: General, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 78928

People

(Reporter: nbi, Assigned: asa)

References

Details

No cursor appears in the text entry field and it is not possible to enter text. If the pop up has an action button it will be greyed out. Check boxes appear unaffected. The URL bar is also unaffected. This bug existed in Netscape 6.x, but not in Netscape 4.73-4.79. Given the impact of this problem it renders the 0.9.8 browser unusable.
Reporter please give an example. I've a simple test case (http://cocoa.eu.org/~thomas/moz/125290.html) and it seems to work correctly.
worksforme with 021403/8 mozilla win32 and linux builds tested at http://cocoa.eu.org/~thomas/moz/125290.html
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Whatever happened to the "steps to reproduce" that I submitted?? The problem is *NOT* fixed and is 100% reproducible! They even occur in Mr. Deniau's test case: 1. Click on "File". 2. Click on "Open File". 3. Try to enter text in the "File name:" field. RESULT = No cursor appears, no text entry possible. 2nd example: 1. Click on "Search". 2. Click on "Find in this page". 3. Try to enter text in the "Find text:" field. RESULT = No cursor appears, no text entry possible. "Find" button is greyed out.
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
*** Bug 133648 has been marked as a duplicate of this bug. ***
Are you able to reproduce with a current nightly and a new profile? (create by starting "mozilla -profilemanager")
A new profile doesn't help. In fact I can't enter text for the profile name so I'm limited to "Default User". Sound familiar? Is there anyone associated with this project capable of providing intelligent and constructive comments that help towards resolving this? For example, "based on your description verify that libxyz is present/current/uncorrupted" or "please try the tests found at....". A comment like "works for me, must be your problem" is *NOT* helpful. If you care to respond, but lack the expertise to address this issue please direct me to someone who can. I have already tried the .9.8 RPM, the .9.8 tar ball, the .9.9 tar ball, and most recently building from .9.9 source. The results being the same in all cases. I'm willing to spend time solving this, but I'm not about to squander my time on a wild goose chase when it seems apparent that no meaningful help is coming my way and the project lacks the expertise to address problems like this. I'll try a nightly build if you can provide a reason as to why it might help. Grasping for straws with 11MB+ downloads over a 32kbps line is simply a no-go. I'm willing to help, but please don't waste my time. Thank you.
Well - being a silly helper only, and no expert - I'll risk wasting your time just one more time: Is your component.reg recent? It will be re-created if missing. No risk in deleting it. (If you have installed to a dir only root has write access to, run all installed components once as root before you start moz as regular user, in order to generate and write a current version of it.) On a default Installer installation, the file is found in /usr/local/mozilla/component.reg If this doesn't help things either, some info about your WM - version and focus settings - might be of interest.
Resolving as duplicate of bug 78928. The hint there is to set option for DecorateTransients in .twmrc Some say that doesn't work for them, however. It also seems that setting "NoTitleFocus" causes havoc. For more details, see the bug and others commented about there. *** This bug has been marked as a duplicate of 78928 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago23 years ago
Resolution: --- → DUPLICATE
QA: Reporter confirms in email: [snipped] "Woohoo, it works! The DecorateTransients, that is."
vrfy
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.