I could be wrong but the problem here is that this implementation of AMP is making a lot of assumptions about the view. Imo, an AMP theme should be specifically coded. There are pieces of code I'm not sure how they'd get into the view, perhaps built with the default theme in mind.Can you pass along the fix by chance? All of our amp pages are now disappearing due to this.
Its on my plate to look into what bd cache does to the views, what code it edits etc, but this has nothing to do with UI.X, but rather the specific implementation of this amp system.
Midpost, I looked around and Mike posted this:
Which essentially means you shouldn't try to shove a complex forum theme into Amp, thats literally what Amp is trying to avoid.Realistically, if we were to try to implement this, you'd likely be looking at an entirely differently styled page because:
One sizable issue is the fact that <img> tags (and all other embeds) require explicit dimensions, which is generally something we don't track. Similarly, media embeds are often done a bit differently, though if they're just iframes they might be ok.
- Markup limits and changes (see more below)
- Limits to some CSS rules (such as overflow)
- Limits of CSS length and inclusion method (50,000 bytes and inlined)
By way of an example, here's a blog entry: http://blog.luxuryrestaurantguide.com/2016/03/03/thefutureoffood3dprinting/
Here's the AMP version of it: http://blog.luxuryrestaurantguide.com/2016/03/03/thefutureoffood3dprinting/amp/
If you accept that it's going to be a very stripped down version of the page and potentially missing some of the standard components you'd see in posts (particularly if there's any sort of more advanced/interactive features added; spoilers would probably be a good example), then it may be doable, but it would still be a significant feature to add (likely requiring a different "view" type entirely).
So, its not something that I could pass as a fix since well by nature of AMP its going to have some limitations and restrictions. I'm not even sure if its something we want to support as its a hack.
ETA: It'd be like @Arty 's email customizer trying to push the entirety of XenForo into an email. Instead, Arty made a new template and pulled variables out of the theme. This imo is proper, and how Amp should be handled.