[Bug 9746] New: Wine's iexplore input fields don't work

http://bugs.winehq.org/show_bug.cgi?id=9746

Summary: Wine's iexplore input fields don't work
           Product: Wine
           Version: 0.9.45.
          Platform: Other
               URL: http://www.genealogy.com
        OS/Version: other
            Status: NEW
          Keywords: download
          Severity: enhancement
          Priority: P2
         Component: wine-shdocvw
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

To repeat, do
wine iexplore http://www.genealogy.com
The input fields are dead, can't select them with the mouse or keyboard.

This is the site Family Tree Maker's online search takes you to.

[Bug 9746] Wine's iexplore input fields don't work

http://bugs.winehq.org/show_bug.cgi?id=9746

Dan Kegel  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|enhancement                 |normal
   Target Milestone|---                         |1.0.0

--- Comment #1 from Dan Kegel   2007-10-07 03:07:48 ---
Aw, c'mon, input fields have to work.  Let's fix this for 1.0.

[Bug 9746] Wine's iexplore input fields don't work

http://bugs.winehq.org/show_bug.cgi?id=9746

Luke Bratch  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #2 from Luke Bratch   2007-10-07 05:15:19 ---
If it helps - you can still put text in the text boxes by highlighting and
dragging text in from elsewhere.

[Bug 9746] Wine's iexplore input fields don't work

http://bugs.winehq.org/show_bug.cgi?id=9746

Simon  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #3 from Simon   2007-10-10 15:44:21 ---
I think this used to work in some versions ago. I´ll try to do a regression
test when I get the time.

[Bug 9746] Wine's iexplore input fields don't work

http://bugs.winehq.org/show_bug.cgi?id=9746

--- Comment #4 from Austin English   2007-10-10 16:39:17 ---
What version last worked?

[Bug 9746] Wine's iexplore input fields don't work

http://bugs.winehq.org/show_bug.cgi?id=9746

--- Comment #5 from Simon   2007-10-10 16:47:21 ---
#4: 0.9.41 works here. I´m compiling 0.9.42 right now, too see if the bug is
present there. It takes forever to compile for me though.

[Bug 9746] Wine's iexplore input fields don't work

http://bugs.winehq.org/show_bug.cgi?id=9746

--- Comment #6 from Simon   2007-10-10 17:13:06 ---
0.9.42 didn´t work, so the bug was introduced somewhere between 0.9.41 and
0.9.42. I´ll do a regression test to see which patch introduced this
regression.

[Bug 9746] Wine's iexplore input fields don't work

http://bugs.winehq.org/show_bug.cgi?id=9746

--- Comment #7 from Simon   2007-10-10 18:56:30 ---
I guess I found some time after all. :)

92b3cab7916445d79d2559e4b580f99e3b0de479 is first bad commit
commit 92b3cab7916445d79d2559e4b580f99e3b0de479
Author: Rob Shearman 
Date:   Tue Jul 24 17:06:42 2007 -0500

mshtml: OleDocumentView_UIActivate should call
IOleInPlaceUIWindow_SetActiveObject and IOleInPlaceFrame_SetBorderSpace.

Add a test to show this behaviour.
    Don't call nsIWebBrowserFocus_Activate when just activating the window.
    Instead call it when UI-activating the window.

:040000 040000 b8ba81ccd31dd254de04966611acb350e258fe43
0a93a75b1e432d50ae1eff1fd89d78bea1811ce3 M      dlls

[Bug 9746] Wine's iexplore input fields don't work

http://bugs.winehq.org/show_bug.cgi?id=9746

Simon  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 9746] Wine's iexplore input fields don't work

http://bugs.winehq.org/show_bug.cgi?id=9746

Jaime Rave  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 9746] Wine's iexplore input fields don't work

http://bugs.winehq.org/show_bug.cgi?id=9746

Douglas E. Warner  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #8 from Douglas E. Warner   2007-10-18 10:29:07 ---
Is there a patch available for this bug?  I believe this also might be
affecting the ability to make changes to forms inside Steam (like my Steam ID).

[Bug 9746] Wine's iexplore input fields don't work

http://bugs.winehq.org/show_bug.cgi?id=9746

--- Comment #9 from Luke Bratch   2007-10-18 16:23:11 ---
Created an attachment (id=8647)
 --> (http://bugs.winehq.org/attachment.cgi?id=8647)
Hack to make text input work

I've just had a little play around and this hack (which just reverses a single
line of that commit that Simon found) fixes text input.

I have no idea if this has broken anything else, but doesn't seem to have.

This doesn't actually seem to allow log in to the "Community" page in Steam
though, but it does work in iexplore.exe outside of Steam.

[Bug 9746] Wine's iexplore input fields don't work

http://bugs.winehq.org/show_bug.cgi?id=9746

--- Comment #10 from Luke Bratch   2007-10-23 12:25:38 ---
Patch submitted:

http://www.winehq.org/pipermail/wine-patches/2007-October/045611.html

[Bug 9746] Wine's iexplore input fields don't work

http://bugs.winehq.org/show_bug.cgi?id=9746

Louis Lenders  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

--- Comment #11 from Louis Lenders   2007-10-23 13:47:11 ---
> Patch submitted:

ok, fixed then

[Bug 9746] Wine's iexplore input fields don't work

http://bugs.winehq.org/show_bug.cgi?id=9746

Louis Lenders  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #12 from Louis Lenders   2007-10-23 13:47:36 ---
closin

[Bug 9746] Wine's iexplore input fields don't work

http://bugs.winehq.org/show_bug.cgi?id=9746

--- Comment #13 from Dan Kegel   2007-10-23 16:26:19 ---
You're not supposed to actually close the bug until the
fix shows up in a release...

[Bug 9746] Wine's iexplore input fields don't work

http://bugs.winehq.org/show_bug.cgi?id=9746

--- Comment #14 from Luke Bratch   2007-10-23 16:29:11 ---
The fix was committed to Git earlier today:

http://source.winehq.org/git/wine.git/?a=commit;h=7ce4194c796788036c1f97c689...

Or do we need to wait for a proper Wine release?

[Bug 9746] Wine's iexplore input fields don't work

http://bugs.winehq.org/show_bug.cgi?id=9746

--- Comment #15 from Louis Lenders   2007-10-23 16:36:32 ---
> You're not supposed to actually close the bug until the
> fix shows up in a release...

As Luke said already the patch was committed, i checked the bug was gone, and i
haven't seen _anyone_ of the maintainers of bugzilla waiting until the  new
release is coming out, once a bug-fix got committed into git.................

[Bug 9746] Wine's iexplore input fields don't work

http://bugs.winehq.org/show_bug.cgi?id=9746

--- Comment #16 from Dan Kegel   2007-10-23 17:22:47 ---
Really?  I almost never notice somebody closing
a bug before release.  Maybe I'm missing lots of
stuff, but I'd really like to stick to that
standard: mark it fixed when it hits git, mark it
closed when it hits a release.

[Bug 9746] Wine's iexplore input fields don't work

http://bugs.winehq.org/show_bug.cgi?id=9746

--- Comment #17 from Luke Bratch   2007-10-23 17:25:06 ---
I may actually have been thinking of things being resolved fixed but not
actually closed straight away.

Either way, I'll remember that for the future.