Forms won't submit when form ID contains a slash about unpoly HOT 7 CLOSED

I've seen one other case where slashes where used (inlining templates in AngularJS).

If it is valid HTML5 we should make some effort to support it with the [id="test/test"] approach.

I believe this could be a small change here:

from unpoly.

If it is valid HTML5 we should make some effort to support it with the [id="test/test"] approach.

Maybe only do that if it is an invalid #... selector as I think doing it that way is slightly slower? The regex I gave above should be able to detect it fine as that was the old HTML4 standard.

from unpoly.

That might be because / is invalid in HTML4 and earlier (although the restriction was lifted in HTML5 I just found out). Initially (and if you want to be sure it works in all browsers) the HTML id attribute is restricted to the set of [a-zA-Z0-9_-]

Using / would be especially problematic as it could prevent an id from being referenced from HTML as well as it could be inferred as a URL path instead of a DOM id depending on implementation.

from unpoly.

I'm assuming submitting such a form would trigger a replacement for form#test/test, which is an invalid CSS selector.

@foobear What's your use case for using slashes in IDs?

from unpoly.

Good point. While form#test/test is an invalid CSS selector, the form ID would still be valid HTML5.

Maybe Unpoly could transform its "default" selector generated by the form ID to something that works, like form[id="test/test"]. However, I am not sure if this could cover all cases and if Unpoly would need to do it.
Throwing an error would be fine for me. Since jQuery or document.querySelector cause an error, I'd have expected to see one, too.

The slashes in IDs already existed in the application "because of reasons". In this case I could change the application to not use slashes in IDs.

from unpoly.

Yeah, definitely only when there's a weird character in the ID.

from unpoly.

Will be fixed in the next release.

from unpoly.