Search and Top Navigation
#11616 closed bug (worksforme)
Opened March 25, 2015 04:17AM UTC
Closed March 25, 2015 12:38PM UTC
right-clicks on the tab and selects to open in new window/tab results in only tab content loaded
| Reported by: | phuongu | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | none |
| Component: | ui.tabs | Version: | 1.11.1 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
I have made an upgrade of JQuery UI from 1.8 to 1.11 in my web applicaiton, which causes a change in behaviour of the tab, where right-clicks on the tab and selects to open in new window/tab results in only tab content loaded. This means that the Url associated with the tab itself is that of the partial that's loaded via ajax rather than the hash associated with the tab.
To my knowledge there has been a changed introduced in jQueryUI v1.9 that is relevant to the issue and also my be relevant to this ticket Ticket #9363
A hint for a fix or workaound would be appreciated.
Attachments (0)
Change History (2)
Changed March 25, 2015 08:46AM UTC by comment:1
Changed March 25, 2015 12:38PM UTC by comment:2
| resolution: | → worksforme |
|---|---|
| status: | new → closed |
That's definitely not happening for me on http://view.jqueryui.com/master/demos/tabs/default.html.
Please provide a reduced test case as requested in the red box if you continue to have problems. We can re-open the ticket if it's reproducible.
I have made an upgrade of JQuery UI from 1.8 to 1.11 in my web applicaiton, which causes a change in behaviour of the tab, where right-clicks on the tab and selects to open in new window/tab results in only tab content loaded. This means that the Url associated with the tab itself is that of the partial that's loaded via ajax rather than the hash associated with the tab.
The issue is that the new page will straight up display the HTML of the ajax response with no CSS styling, JavaScript, or anything.
To my knowledge there has been a change introduced in jQueryUI v1.9 that is relevant to the issue and also might be relevant to Ticket #9363
A hint for a fix or workaound would be appreciated.