Closed Bug 177681 Opened 22 years ago Closed 6 years ago

gtkmozembed fails to give inputfocus to javascript:prompt() windows

Categories

(Core Graveyard :: Embedding: GTK Widget, defect)

x86
Linux
defect
Not set
normal

Tracking

(tracking-b2g:backlog)

RESOLVED WONTFIX
tracking-b2g backlog

People

(Reporter: peter.budek, Assigned: blizzard)

Details

User-Agent:       Mozilla/4.73 [de] (X11; I; Linux 2.2.17 i586)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021016

There ist now way to enter a text in windows which are generated by
javascript:prompt(...); .

Reproducible: Always

Steps to Reproduce:
1. Run TestGtkEmbed
2. enter javascript:prompt("Text", "");
3. try to enter something in the text field of the new window

Actual Results:  
no focus

Expected Results:  
focus
Still present in
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021114

If 'prompt("text1", "text2");' is entered as a command in the
javascript-console, it works fine! It does not work, if 
'javascrip:prompt("text1", "text2");' ist entered as a url in TestGtkEmbed.
It also does not work, if 'javascrip:prompt("text1", "text2");' is a
part of a HTML-document.
If also works if a chrome ist loaded in TestGtkEmbed
(eg. chrome://navigator/component/navigator.xul) and
'javascript:prompt("text1", "text2");' is entered afterwards in
the URL-Filed of TestGtkEmbed.

Is this an initialisation problem?
I can confirm this for gtkmozembed from 1.02, 1.2, 1.2.1, 1.3a, 1.3, and 1.4 RC1
and RC2 (basically, it hasn't worked since 1.0).  Is any progress being made on
this?
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/
The bug is still there - with the exact same sequence to reproduce it -
in our product built on top of Mozilla 1.7.8 distribution.


(In reply to comment #4)
> 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/
> 

WFM in linux/gtk2 build: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1)
Gecko/20050920 Firefox/1.6a1 
our application uses gtk and not gtk2. 
embedding framework is different in gtk vs. gtk2.

switching to gtk2 is not a feasible option for us.
QA Contact: pavlov → gtk-widget
Product: Core → Core Graveyard
[Tracking Requested - why for this release]:
Embedding: GTK Widget isn't a thing, closing.
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.