gatsby-offline-plugin add as="fetch" to Link, cause W3C error

[Steffi3rd]

Bad value fetch for attribute as on element link.

package.json

[kakadiadarpan]

@Steffi3rd I'm not sure why that is happening. As per the Mozilla standard, fetch is a correct value for "as" in case of a JSON file.

[LekoArts]

Is W3C even relevant? I'd just ignore it. The times are over when people had W3C banners on their site 😂

[gatsbot[bot]]

Old issues will be closed after 30 days of inactivity. This issue has been quiet for 20 days and is being marked as stale. Reply here or add the label "not stale" to keep this issue open!

[gatsbot[bot]]

Hey again!

It’s been 30 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it.

Please keep in mind that I’m only a robot, so if I’ve closed this issue in error, I’m HUMAN_EMOTION_SORRY. Please feel free to reopen this issue or create a new one if you need anything else.

Thanks again for being part of the Gatsby community!

[derykl]

I'd still like a better answer to this than laughing at the notion of HTML validity.

Is W3C really not relevant these days? Seems it to me - the only way to ensure all browsers correctly render given HTML is surely to all work to the same agreed standard. Anyone old enough to remember Internet Explorer 6 ought to remember the absolute chaos that came from everyone ignoring standards and only developing to a method of "well it works for me in my browser". Do we really want to run the risk of having, say, Chrome becoming the next IE6 in terms of breaking the web for other browsers such as Firefox?

AFAIK, valid code is also a requirement for the A level of WCAG which can be required by accessibility laws in some countries.

[kapilgorve]

I also ran into this issue. I have created an issue on validator.
https://github.com/validator/validator/issues/960

[kapilgorve]

@LakesGeek It's fixed now. Validator wont show error for this.

[derykl]

Brilliant - never occurred to me that the validator itself was wrong! Thanks for passing it on to the right place.

[nikant25]

@kapilgorve _It's fixed now. Validator wont show error for this._

However, the validator test today 2020-11-10 shows this error:

Is there a way to win?

[kapilgorve]

Not sure how html attributes work. I can see that your values are not in quotes. Maybe that's an issue ? @nikant25

[nikant25]

@kapilgorve The same result with quotes:
_Error: Bad value fetch for attribute as on element link.

From line 12, column 1; to line 12, column 195

th:30em)>↩<link rel=preload href=https://eutourdata.com/fortif/germ/data/arlfort/arlfortanno.jsonld type='application/ld+json;profile="http://www.w3.org/ns/anno.jsonld"' as="fetch" crossorigin="anonymous">↩

Error: Bad value fetch for attribute as on element link.

From line 13, column 1; to line 13, column 151

onymous">↩↩

[kapilgorve]

@nikant25 I can see your rel attribute is not enclosed in quotes.

[nikant25]

@kapilgorve There are many unquoted elements in the meta preload that are valid. However, for clarification, I have set the quotes, but the result is the same:
Error: Bad value fetch for attribute as on element link.

From line 12, column 1; to line 12, column 199

th:30em)>↩↩

Error: Bad value fetch for attribute as on element link.

From line 13, column 1; to line 13, column 155

onymous">↩↩