-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Faces 4.0: OutputScript/OutputStyleSheet Remove 'type' attribute if HTML5 #1565
Comments
Good point! |
These are indeed optional in HTML5 but not in HTML4 (although the average webbrowser is lenient in this). Also note that the same "issue" applies to |
Yep but with the Death of IE. Should Faces 4.0 just be an HTML5+ supporting framework? |
There should be a way for the HTML renderers to detect the doctype currently used. Facelets is capable of this but this is nowhere specified in Faces (as far as I see/know). Blindly removing it would break validity of (existing) HTML4 pages. |
Ok detecting HTML5 doctype would be ideal. It would also be a nice addition to Faces |
Doctype processing is already specced in section 1.1.1.1 of appendix A of the spec, but it's only specced as part of Facelets config. I'm currently having difficulty where to add it to the Faces API. Neither |
I've for the time being made it an implementation detail. If someone knows a valid and sensible API method for this then I'm all ears to add. |
@tandraschko any thoughts on this one? |
After meditating a night on this one I think the closest candidate is |
|
I like your plan @BalusC |
MyFaces PR: apache/myfaces#198 Closing this ticket as its now implemented in MyFaces and Mojarra 4.0 |
For Faces 4.0 I would like to remove the
type="text/javascript"
from h:outputScript as its completely unnecessary in the DOM and there is only 1 kind of scriptW3C Validator warnings:
I think we should also remove it from OmniFaces 4.0 and PrimeFaces 11.0 in the spots it used.
I can submit PR's for Mojarra and MyFaces if acceptable?
cc @OBreidenbach who reported this originally here: primefaces/primefaces#4135
The text was updated successfully, but these errors were encountered: