Closed
Bug 78610
Opened 24 years ago
Closed 24 years ago
winEmbed: can't type in form fields
Categories
(Core Graveyard :: Embedding: APIs, defect)
Core Graveyard
Embedding: APIs
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla0.9.2
People
(Reporter: edburns, Assigned: adamlock)
References
()
Details
Attachments
(1 file)
(deleted),
patch
|
Details | Diff | Splinter Review |
Users of Webclient, winEmbed, and probably all other embedding apps can no
longer type in text fields in a form!
Reproducible: Always
Steps to reproduce:
1. Build winEmbed, or webclient on Linux (other embedding apps probably will
feel the same bug).
2. Visit http://bugzilla.mozilla.org/
3. Click on the text field.
No cursor appears, and you can't type.
This is a real bummer.
Comment 1•24 years ago
|
||
In my case, in SkipStone, it happens almost all the time but clicking around the
page then reclicking in an entry shows the cursor, its annoying nontheless..
Comment 2•24 years ago
|
||
ccing blizzard :)
Comment 3•24 years ago
|
||
*** This bug has been marked as a duplicate of 76617 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
I'm reopening this since ccarlen closed 76617 and I'm still seeing the problem
with today's trunk.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
I'm still seeing this with winEmbed with yesterday's trunk.
This bug is killing me. Can someone please fix it or give me some clues about
how to fix it?
Thanks,
Ed
Severity: critical → blocker
Target Milestone: --- → mozilla0.9.1
See bug 71014 for the code that embedders need to insert to do focus.
winEmbed doesn't have it which is why focus doesn't work. mfcEmbed does have it
and works as expected.
I'm renaming this bug to cover just winEmbed
Summary: Embedding App: can't type in form fields → winEmbed: can't type in form fields
Patch fixes the problem with setting focus when the window is activated. A
new comment to bug 64349 suggests there may still be problems cycling between
the address field and HTML forms, but this fixes the biggest issue.
Adam, I need an explanation of why I suddenly have to introduce non-xp code into
my embedding app when I never needed it before? Until recently, this "just
worked". Now, what you're saying I must do is make some platform specific
modifications to me embedding app. That really bites. Currently, in my
webclient embedding app, there is no code whatsoever that handles any WM_*
messages. I have no idea where such code would be inserted, since we don't have
a message proc in our app. Please see mozilla/java/webclient/src_moz.
Reporter | ||
Comment 10•24 years ago
|
||
Adam, thanks for your response, but the fact that I have to do this now just to
get forms to work for the user is a major regression in my opinion. Can't the
embedding APIs do this for me? Can someone please explain the rationale for
requiring Embedding apps to do this, especially since it worked before.
Comment 11•24 years ago
|
||
Ed, pls try this patch. It enables me to type inside forms on Solaris. If you
accept this patch, pls give me ra and I'll check it in.
Index: mozilla/java/webclient/src_moz/CBrowserContainer.cpp
===================================================================
RCS file: /cvsroot/mozilla/java/webclient/src_moz/CBrowserContainer.cpp,v
retrieving revision 1.19
diff -u -r1.19 CBrowserContainer.cpp
--- CBrowserContainer.cpp 2001/05/10 20:47:06 1.19
+++ CBrowserContainer.cpp 2001/05/10 22:58:53
@@ -28,6 +28,7 @@
#include "CBrowserContainer.h"
#include "nsCWebBrowser.h"
#include "nsIWebBrowser.h"
+#include "nsIWebBrowserFocus.h"
#include "nsIRequest.h"
#include "nsIDOMNamedNodeMap.h"
#include "nsIDOMWindow.h"
@@ -619,6 +620,10 @@
nsresult JNICALL
CBrowserContainer::doEndDocumentLoad(nsIWebProgress *aWebProgress)
{
+
+ nsCOMPtr<nsIWebBrowserFocus> focus(do_GetInterface(mInitContext->webBrowser));
+ focus->Activate();
+
nsCOMPtr<nsIDOMWindow> domWin;
if (nsnull != aWebProgress) {
Assignee | ||
Comment 12•24 years ago
|
||
I agree that you shouldn't need to put any code into the client to activate the
browser when someone clicks on it.
However it is the client's responsibility to activate the browser window when
the containing frame is activated. The patch I submitted does that latter.
We still have to resolve the "clicking on the browser does not give focus"
issue, but applying the patch or similar to your own code means at least you
can type into form fields even if you have to switch away from the app and back
again.
Reporter | ||
Comment 13•24 years ago
|
||
Works on win32 as well. ra=edburns. Great work Ashu.
Reporter | ||
Comment 14•24 years ago
|
||
By the way. I'm typing this using Webclient.
Comment 15•24 years ago
|
||
patch checked into Webclient. Adam, if you have checked in the patch for
winEmbed, pls close this Bug. thnx.
Assignee | ||
Comment 16•24 years ago
|
||
If someone wants to review my patch, I'll be happy to checkin. winEmbed is only
a test app so no sr should be required.
Comment 17•24 years ago
|
||
Looks okay, r=jag
Assignee | ||
Comment 18•24 years ago
|
||
Fix for winEmbed is checked in. Larger problem that clicking on form fields
in embedding apps doesn't work is still outstanding.
Comment 19•24 years ago
|
||
I think saari had some other bug about windows embedding and widgets...
Comment 20•24 years ago
|
||
*** Bug 81729 has been marked as a duplicate of this bug. ***
Assignee | ||
Comment 21•24 years ago
|
||
Moving to 0.9.2. This bug will be closed off when I find the other bugs dealing
with the outstanding problems.
Status: REOPENED → ASSIGNED
Target Milestone: mozilla0.9.1 → mozilla0.9.2
Assignee | ||
Comment 22•24 years ago
|
||
Remaining focus problems covered by 83201
Status: ASSIGNED → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•