EggXpert

It's not that big of a deal, but I find myself sometimes staring at the screen waiting for a search to take place, when nothing's loading or anything.

It's an easy bug to replicate - go to the search bar at the top of the window, type in a search term, and press the Enter key.  While the Enter key would usually cause a search box to search the desired content, it just sits there in Opera.  I have to manually click the yellow 'Go' arrow (how tedious, I know!).

Seriously, though, it's not a big deal, but this is one of those little things that probably should be reported. :)  I searched around, and it doesn't seem to have been reported yet... Sorry if this is a duplicate.

Also, if it doesn't work in Opera, there's a possibility that it doesn't work in other standard-compliant browsers.

Thanks!

Hmmm. Seems to work fine in FireFox and IE..

 

I said 'standard-compliant'. ;)

I figured as much.

I figgered it out. xD

This line:

<input name="ctl00$ctl01$bhcr$t$_$TitleBarSearchText" type="text" maxlength="64" size="15" id="ctl00_ctl01_bhcr_t___TitleBarSearchText" onkeydown="KeyDownHandlerctl00_ctl01_bhcr_t___TitleBarSearchButton(event);" />

on line 91 needs to have 'onkeydown' changed to 'onkeypress'.  If I remember correctly, Opera's keydown functionality is odd, whether it's a compliancy issue (them following rules) or a bug (them not knowing).

If someone could look into this, I'd grealy appreciate it. :)  I don't think it would take three seconds.  (I have no reason to think that it wouldn't work everywhere else, too.)

Edit: And by this line (91), I'm referring to the line number in the homepage's source, just so you know.  Thanks!

TheLarrikin:

I figgered it out. xD

This line:

<input name="ctl00$ctl01$bhcr$t$_$TitleBarSearchText" type="text" maxlength="64" size="15" id="ctl00_ctl01_bhcr_t___TitleBarSearchText" onkeydown="KeyDownHandlerctl00_ctl01_bhcr_t___TitleBarSearchButton(event);" />

on line 91 needs to have 'onkeydown' changed to 'onkeypress'. If I remember correctly, Opera's keydown functionality is odd, whether it's a compliancy issue (them following rules) or a bug (them not knowing).

If someone could look into this, I'd grealy appreciate it. :) I don't think it would take three seconds. (I have no reason to think that it wouldn't work everywhere else, too.)

Edit: And by this line (91), I'm referring to the line number in the homepage's source, just so you know. Thanks!

 

He even identified the bug, owned . Maybe that change will fix the Konqueror browser's inability to click buttons.
 

Do you have a download link for Konqueror?  I'd be interested in figuring it out.

I'm pretty sure it is Linux (being more specific, KDE) exclusive at the moment. I read somewhere they are working on a Windows version but it wouldn't have the latest things the native one does.

Here is the link to a detailed bug report I posted not too long ago: http://www.eggxpert.com/forums/thread/157290.aspx

 

:)  Thanks.  I'll look into it.

Thanks Larrikin.  I've reported the problem to our dev team.