-
Notifications
You must be signed in to change notification settings - Fork 140
touch devices: open submenus on the desktop horizontal menu #949
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This works fine for me and corrects the problem detailed in the issue
@carolinan This fix is not working for me. I'm getting a JS error: |
@westonruter I'm afraid that I missed this when I merged :( I will try and look at this as soon as I can but if you have any ideas for a fix then let me know. |
@pattonwebz I'm opening a PR. |
Thank you for this 🙌 ❤️ Also as an aside I know you have been working to make sure this theme is AMP compatible and if there are other JS changes required for that let me know as we still have a very small window for adjusting important aspects and being AMP ready is important in my view |
@pattonwebz See #971. Otherwise, the theme has been made fully AMP compatible via the AMP plugin thanks to great work by @schlessera: ampproject/amp-wp#3342, ampproject/amp-wp#3403, ampproject/amp-wp#3606, ampproject/amp-wp#3604, ampproject/amp-wp#3616, ampproject/amp-wp#3628, ampproject/amp-wp#3621, ampproject/amp-wp#3618, ampproject/amp-wp#3617, ampproject/amp-wp#3620, ampproject/amp-wp#3594, ampproject/amp-wp#3578, ampproject/amp-wp#3574, ampproject/amp-wp#3570, ampproject/amp-wp#3569, ampproject/amp-wp#3559 In lieu of the Twenty Twenty theme being AMP-compatible in and of itself, the AMP plugin shims the compatibility via its core theme sanitizer. Perhaps in the future new core themes could be developed leveraging AMP components (especially when they can be installed locally as node packages via Bento AMP). But in the meantime, it's not so bad to maintain AMP compatibility for the core themes externally since they don't really change over time. |
Hopefully Fixes #790