-
Notifications
You must be signed in to change notification settings - Fork 14
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
w3c check has warnings/errors #130
Labels
Comments
mvitz
added a commit
to mvitz/statuses
that referenced
this issue
Dec 8, 2014
- fixes format of time's datetime attribute - adds moment.js for displaying relative date - uses bootstrap for tooltip with absolute date Relates to innoq#130.
mvitz
added a commit
to mvitz/statuses
that referenced
this issue
Mar 13, 2015
Specifying the charset prevents the browser from guessing the charset to use. Relates to innoq#130.
mvitz
added a commit
to mvitz/statuses
that referenced
this issue
Mar 13, 2015
Instead of a header with role navigation now the HTML5 element nav is used. Relates to innoq#130.
mvitz
added a commit
to mvitz/statuses
that referenced
this issue
Mar 13, 2015
Removes warnings from w3c validator that label and input are not valid inside an a element. Because preferences aren't links anyway this increases semantic as well. Relates to innoq#130.
mvitz
added a commit
to mvitz/statuses
that referenced
this issue
Mar 13, 2015
By default hiccup generates an id for every form field. In our case (more than one form with method DELETE on the same page) this leads to non unique ids which leads to w3c validation errors. Relates to innoq#130. Workaround for weavejester/hiccup#109.
mvitz
added a commit
to mvitz/statuses
that referenced
this issue
Mar 13, 2015
Only inline elements may be contained whithin inline elements. Because form is not an inline element this leads to w3c validation errors. Relates to innoq#130.
mvitz
added a commit
to mvitz/statuses
that referenced
this issue
Apr 3, 2015
Specifying the charset prevents the browser from guessing the charset to use. Relates to innoq#130.
mvitz
added a commit
to mvitz/statuses
that referenced
this issue
Apr 3, 2015
Instead of a header with role navigation now the HTML5 element nav is used. Relates to innoq#130.
mvitz
added a commit
to mvitz/statuses
that referenced
this issue
Apr 3, 2015
Removes warnings from w3c validator that label and input are not valid inside an a element. Because preferences aren't links anyway this increases semantic as well. Relates to innoq#130.
mvitz
added a commit
to mvitz/statuses
that referenced
this issue
Apr 3, 2015
By default hiccup generates an id for every form field. In our case (more than one form with method DELETE on the same page) this leads to non unique ids which leads to w3c validation errors. Relates to innoq#130. Workaround for weavejester/hiccup#109.
mvitz
added a commit
to mvitz/statuses
that referenced
this issue
Apr 3, 2015
Only inline elements may be contained whithin inline elements. Because form is not an inline element this leads to w3c validation errors. Relates to innoq#130.
mvitz
added a commit
to mvitz/statuses
that referenced
this issue
Apr 8, 2015
Specifying the charset prevents the browser from guessing the charset to use. Relates to innoq#130.
mvitz
added a commit
to mvitz/statuses
that referenced
this issue
Apr 8, 2015
Instead of a header with role navigation now the HTML5 element nav is used. Relates to innoq#130.
mvitz
added a commit
to mvitz/statuses
that referenced
this issue
Apr 8, 2015
Removes warnings from w3c validator that label and input are not valid inside an a element. Because preferences aren't links anyway this increases semantic as well. Relates to innoq#130.
mvitz
added a commit
to mvitz/statuses
that referenced
this issue
Apr 8, 2015
By default hiccup generates an id for every form field. In our case (more than one form with method DELETE on the same page) this leads to non unique ids which leads to w3c validation errors. Relates to innoq#130. Workaround for weavejester/hiccup#109.
mvitz
added a commit
to mvitz/statuses
that referenced
this issue
Apr 8, 2015
Only inline elements may be contained whithin inline elements. Because form is not an inline element this leads to w3c validation errors. Relates to innoq#130.
mvitz
added a commit
to mvitz/statuses
that referenced
this issue
Apr 22, 2015
Specifying the charset prevents the browser from guessing the charset to use. Relates to innoq#130.
mvitz
added a commit
to mvitz/statuses
that referenced
this issue
Apr 22, 2015
Instead of a header with role navigation now the HTML5 element nav is used. Relates to innoq#130.
mvitz
added a commit
to mvitz/statuses
that referenced
this issue
Apr 22, 2015
Removes warnings from w3c validator that label and input are not valid inside an a element. Because preferences aren't links anyway this increases semantic as well. Relates to innoq#130.
mvitz
added a commit
to mvitz/statuses
that referenced
this issue
Apr 22, 2015
By default hiccup generates an id for every form field. In our case (more than one form with method DELETE on the same page) this leads to non unique ids which leads to w3c validation errors. Relates to innoq#130. Workaround for weavejester/hiccup#109.
mvitz
added a commit
to mvitz/statuses
that referenced
this issue
Apr 22, 2015
Only inline elements may be contained whithin inline elements. Because form is not an inline element this leads to w3c validation errors. Relates to innoq#130.
mvitz
added a commit
to mvitz/statuses
that referenced
this issue
May 1, 2015
Specifying the charset prevents the browser from guessing the charset to use. Relates to innoq#130.
mvitz
added a commit
to mvitz/statuses
that referenced
this issue
May 1, 2015
Instead of a header with role navigation now the HTML5 element nav is used. Relates to innoq#130.
mvitz
added a commit
to mvitz/statuses
that referenced
this issue
May 1, 2015
Removes warnings from w3c validator that label and input are not valid inside an a element. Because preferences aren't links anyway this increases semantic as well. Relates to innoq#130.
mvitz
added a commit
to mvitz/statuses
that referenced
this issue
May 1, 2015
By default hiccup generates an id for every form field. In our case (more than one form with method DELETE on the same page) this leads to non unique ids which leads to w3c validation errors. Relates to innoq#130. Workaround for weavejester/hiccup#109.
mvitz
added a commit
to mvitz/statuses
that referenced
this issue
May 1, 2015
Only inline elements may be contained whithin inline elements. Because form is not an inline element this leads to w3c validation errors. Relates to innoq#130.
mvitz
added a commit
to mvitz/statuses
that referenced
this issue
Nov 23, 2015
Specifying the charset prevents the browser from guessing the charset to use. Relates to innoq#130.
mvitz
added a commit
to mvitz/statuses
that referenced
this issue
Nov 23, 2015
Instead of a header with role navigation now the HTML5 element nav is used. Relates to innoq#130.
mvitz
added a commit
to mvitz/statuses
that referenced
this issue
Nov 23, 2015
Removes warnings from w3c validator that label and input are not valid inside an a element. Because preferences aren't links anyway this increases semantic as well. Relates to innoq#130.
mvitz
added a commit
to mvitz/statuses
that referenced
this issue
Nov 23, 2015
By default hiccup generates an id for every form field. In our case (more than one form with method DELETE on the same page) this leads to non unique ids which leads to w3c validation errors. Relates to innoq#130. Workaround for weavejester/hiccup#109.
mvitz
added a commit
to mvitz/statuses
that referenced
this issue
Nov 23, 2015
Only inline elements may be contained whithin inline elements. Because form is not an inline element this leads to w3c validation errors. Relates to innoq#130.
mvitz
added a commit
to mvitz/statuses
that referenced
this issue
Mar 10, 2016
Specifying the charset prevents the browser from guessing the charset to use. Relates to innoq#130.
mvitz
added a commit
to mvitz/statuses
that referenced
this issue
Mar 10, 2016
Instead of a header with role navigation now the HTML5 element nav is used. Relates to innoq#130.
mvitz
added a commit
to mvitz/statuses
that referenced
this issue
Mar 10, 2016
Removes warnings from w3c validator that label and input are not valid inside an a element. Because preferences aren't links anyway this increases semantic as well. Relates to innoq#130.
mvitz
added a commit
to mvitz/statuses
that referenced
this issue
Mar 10, 2016
By default hiccup generates an id for every form field. In our case (more than one form with method DELETE on the same page) this leads to non unique ids which leads to w3c validation errors. Relates to innoq#130. Workaround for weavejester/hiccup#109.
mvitz
added a commit
to mvitz/statuses
that referenced
this issue
Mar 10, 2016
Only inline elements may be contained whithin inline elements. Because form is not an inline element this leads to w3c validation errors. Relates to innoq#130.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I just checked the generated updates page with http://validator.w3.org/check and there seems to be some warnings and errors.
Warnings:
Errors:
…es</a></li><li><a name="inline-images"><span class="fa fa-cogs"></span><label …
…</span><label for="pref-inline-images">Inline images?</label><input class="pre…
…e-images" type="checkbox" value="true"></a></li></ul></div></div></header><mai…
…n confirm('Delete status?')"><input id="_method" name="_method" type…
…time="Thu, 20 Nov 2014 12:20:18 +0100">2014-11-20 12:20:18</time></a></span></…
…"_method" type="hidden" value="DELETE"><button class="btn btn-delete" type="su…
The text was updated successfully, but these errors were encountered: