Closed rbdietz closed 4 years ago
I've noticed this happening periodically too.
Related item(s) worth mentioning:
When the archive module is the first to render a page after a cache rebuild, the ID's on the search form input are given different names. Instead of "edit-actions" and "edit-submit", the archive module causes the render to use "edit-actions--2" and "edit-submit--2"
Because we use the "edit-actions" and "edit-submit" IDs as CSS selectors, these properties never get applied to the elements, and the display wonks (technical term) out.
When some other page is the first render after cache clear, the archive route actually renders invalid HTML. The search form up at the top of the screen and the data navigation form for the archive listing both have elements with the same ID attribute (which is not valid and will cause CSS problems)
I don't know if we can prevent Drupal from rendering invalid HTML. Instead, I think we're going to have to try to avoid using the problematic IDs in CSS selectors.
This bug was reported in Drupal 7 and 8: Drupal 7 https://www.drupal.org/project/drupal/issues/2594955 Drupal 8 https://www.drupal.org/project/drupal/issues/2497909
Proposed fix in PR #189
Search button is misaligned in Chrome for Mac.