Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#8693 closed bug (notabug)

Bug with Autocomplete and HTML in SELECT

Reported by: bugtester Owned by: bugtester
Priority: minor Milestone: 1.10.0
Component: ui.autocomplete Version: 1.9.0
Keywords: Cc:
Blocked by: Blocking:

Description

Hi. I have read this:

"If you find a regression from the 1.8 API, please report it in the bug tracker. Even though the 1.8 API is deprecated, it's important for 1.9 releases not to regress so that users are encouraged to upgrade even if they're not ready to use the new APIs."

Here is my important problem. ;)

jQuery UI 1.8.24 http://jsfiddle.net/7V2Xa/

jQuery UI 1.9.0 http://jsfiddle.net/xK3V5/1/

Steps:

  • input "a" in input box
  • click on item "AAA"

In Version 1.8.24 nothing happen thanks "return false"(?) but in 1.9.0 its loading the website. Is here a way to fix this?

Change History (6)

comment:1 Changed 7 years ago by mikesherov

Owner: set to bugtester
Status: newpending

Thanks for the test case and contributing! I can not reproduce the issue as described in Chrome 22.0.1229.94 . Please let me know what browser this fails in so we can reproduce the issue.

Thanks again!

comment:2 Changed 7 years ago by bugtester

Status: pendingnew

I use the newest versions of Opera, FF and Chrome and old IE8.. all browsers refresh the frame of jsfiddle. Chrome "fakes" here. Look at his tab-icons and you see Chrome reload the jsfiddle tab too. Test it on a html without jsfiddle framework and you jump to google.com for "AAA".

Last edited 7 years ago by bugtester (previous) (diff)

comment:3 Changed 7 years ago by Scott González

Resolution: notabug
Status: newclosed

This is not a bug. Prevent the default action of the anchor click if that's what you want. Please ask for help on the forums or StackOverflow.

comment:4 Changed 7 years ago by bugtester

This is not a bug? In all previous versions of jQuery UI(the last 2 years) its working fine, since 1.9.0 no longer?

Last edited 7 years ago by bugtester (previous) (diff)

comment:5 Changed 7 years ago by Scott González

There has never been any indication that this would do what you're trying to accomplish. The fact that it used to work is coincidence. What makes you think that the public API would make this work? You're not even using the built-in renderer, so you already have non-standard behavior.

comment:6 Changed 7 years ago by bugtester

You're right. I will add event.preventDefault(); Thanks for your fast support.

Last edited 7 years ago by bugtester (previous) (diff)
Note: See TracTickets for help on using tickets.