Iām aware that AMP pages donāt validate in the conventional way that hml5 does, though I donāt know exactly what is and is not valid in AMP. But there are quite a few (html5) validation errors in there.
I thought the differences were mainly a few amp specific elements and attributes. But some errors I see are things lke conventional element nesting issues and whitespace in IDs.
This alternative validation is one thing about AMP I was curious about. As in Iām sure Googleās own browsers would accept and interpret it correctly, but how will other browsers read it?
It seems AMP validation is not as straightforward as one would hope.
Valid amp tags may fail conventional validation.
But it seems the amp validator will let ordinary validation errors slip through, as if it is only checking the amp compliance, not validation overall.
It seems AMP validation is not as straightforward as one would hope.
Valid amp tags may fail conventional validation.
I agree and have found several similar anomalies.
I am convinced Googleās approach of creating the new technique and to disregard the tried and tested W3.org validation tools is hindering Amp progress.
That has been my concern with AMP. If they medal with the spec, then do they expect all the makers of all the other browsers to support their version of it?
I discovered how to create the alternative amp-canonical link also minus JavaScript The ābodyā content, associated files and CSS are validated and the same files used in the AMP version. Notice the .php7 file extension. The top menu home link calls the AMP version.
I still donāt see the transition effect thatās in the demoā¦is that OK with you? Or is just the open/close you were looking for (at which point, I embarassingly admit I misunderstood the problemā¦)
The original problem of not opening was solved and I tried changing the colors and tied myself in knots.
Also the copy I made was jumping all over the page.
Now it does not jump, the color scheme is more to my liking but still requires some tedious tweaking
Edit:
The long term plan is to select a component, only about five now available, enter a couple of essential parameters such as title and the style sheet. Allow the user to edit the generated sample. Submit and render the modified template so the user can copy and paste the complete AMP page to run on their own server.
At the moment available tutorials and demos are clunky.