Skip to content
This repository has been archived by the owner on Oct 8, 2021. It is now read-only.

id=, data-id=, not being respected/tested first ? #3248

Closed
itechnology opened this issue Dec 12, 2011 · 1 comment
Closed

id=, data-id=, not being respected/tested first ? #3248

itechnology opened this issue Dec 12, 2011 · 1 comment

Comments

@itechnology
Copy link

There seems to be a problem with duplicate pages appearing in the dom under certain circumstances, and once this happens, all js dealing with selectors stops working because of dupe element id's

The problem seems to be that data-url seems to be acting like the godly id attribute.

If i go to a page, for example: /somepage?somevar=somevalue, it gets loaded into the dom with data-url="/somepage?somevar=somevalue"

Now if i go to this page again, but access it via /somepage only, we get a duplicate entry in the dom ... one with: data-url="/somepage?somevar=somevalue", and another one with: data-url="/somepage"

I tried setting the id of the div, the data-id on the div, and even data-dom-cache="false", nothing seems to break this behavior.

JQM should probably be checking id/data-id before relying on data-url, or something like that 1st ?

@johnbender
Copy link
Contributor

@itechnology

We've addressed this issue elsewhere (#2784).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant