Title: Keith's Replies | WordPress.org

---

# Keith

  [  ](https://wordpress.org/support/users/keithlang/)

 *   [Profile](https://wordpress.org/support/users/keithlang/)
 *   [Topics Started](https://wordpress.org/support/users/keithlang/topics/)
 *   [Replies Created](https://wordpress.org/support/users/keithlang/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/keithlang/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/keithlang/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/keithlang/engagements/)
 *   [Favorites](https://wordpress.org/support/users/keithlang/favorites/)

 Search replies:

## Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)

 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Gutenberg & Yoast seo scrolling issue](https://wordpress.org/support/topic/gutenberg-yoast-seo-scrolling-issue/)
 *  [Keith](https://wordpress.org/support/users/keithlang/)
 * (@keithlang)
 * [7 years, 5 months ago](https://wordpress.org/support/topic/gutenberg-yoast-seo-scrolling-issue/#post-11227228)
 * This appears to be a bug with Gutenberg. It has to do with the overflow of the
   editor view in CSS (Don’t hit me up about incorrect terminology please!).
    But
   with a bit of hacking I got this to work
 * Add to functions.php
 *     ```
       add_action('admin_head', 'my_scroll_admin_fix');
   
       function my_scroll_admin_fix() {
         echo '<style>
           #wpwrap .edit-post-visual-editor .editor-writing-flow {
           max-width: calc( 1200px - 40px );
   
               overflow: visible;
       }
         </style>';
       }
       ```
   
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[AMP] Google Errors with AMP](https://wordpress.org/support/topic/google-errors-with-amp/)
 *  [Keith](https://wordpress.org/support/users/keithlang/)
 * (@keithlang)
 * [10 years, 2 months ago](https://wordpress.org/support/topic/google-errors-with-amp/#post-7405455)
 * I’m no AMP expert but if you haven’t already tried these tools they might lead
   you to discover why you’re getting the messages. I got one or two but they were
   structure errors.
 * But first of all, you’re getting lots of https errors and I see you’re using 
   CloudFlare. Maybe try to remove the AMP pages from the CDN?
 * use #development=1 after the URL, open Chrome and then developer tools and put
   it in Mobile Emulation mode and check for AMP validation errors on the console.
 * Structured data tool
    [https://search.google.com/structured-data/testing-tool/u/0/](https://search.google.com/structured-data/testing-tool/u/0/)

Viewing 2 replies - 1 through 2 (of 2 total)