110 failed [chromium] › editor/blocks/missing.spec.js:11:2 › missing block › should strip potentially malicious on* attributes [chromium] › editor/blocks/missing.spec.js:33:2 › missing block › should strip potentially malicious script tags [chromium] › editor/blocks/navigation-colors.spec.js:57:2 › Navigation colors › All navigation links should default to the body color and submenus and mobile overlay should default to a white background with black text [chromium] › editor/blocks/navigation-colors.spec.js:78:2 › Navigation colors › Top level navigation links inherit the text color from the theme/group but do not apply to the submenu or overlay text [chromium] › editor/blocks/navigation-colors.spec.js:131:2 › Navigation colors › Navigation text does not inherit the link color from the theme/group [chromium] › editor/blocks/navigation-colors.spec.js:187:2 › Navigation colors › The navigation text color should apply to all navigation links including submenu and overlay text [chromium] › editor/blocks/navigation-colors.spec.js:229:2 › Navigation colors › The navigation background color should apply to all navigation links including submenu and overlay backgrounds [chromium] › editor/blocks/navigation-colors.spec.js:274:2 › Navigation colors › As a user I expect my navigation to use the colors I selected for it [chromium] › editor/blocks/navigation-frontend-interactivity.spec.js:45:3 › Navigation block - Frontend interactivity › Overlay menu › Overlay menu interactions [chromium] › editor/blocks/navigation-frontend-interactivity.spec.js:91:3 › Navigation block - Frontend interactivity › Overlay menu › Overlay menu interactions in Safari (@WebKit) [chromium] › editor/blocks/navigation-frontend-interactivity.spec.js:161:3 › Navigation block - Frontend interactivity › Submenu mouse and keyboard interactions › Submenu interactions [chromium] › editor/blocks/navigation-frontend-interactivity.spec.js:260:3 › Navigation block - Frontend interactivity › Submenu mouse and keyboard interactions › Submenu interactions on Safari (@WebKit) [chromium] › editor/blocks/navigation-frontend-interactivity.spec.js:368:3 › Navigation block - Frontend interactivity › Submenus (Arrow setting) (@Firefox, @WebKit) › submenu click on the arrow interactions [chromium] › editor/blocks/navigation-frontend-interactivity.spec.js:458:3 › Navigation block - Frontend interactivity › Page list block (@Firefox, @WebKit) › page-list submenu user interactions [chromium] › editor/blocks/navigation-list-view.spec.js:49:2 › Navigation block - List view editing › show a list view in the inspector controls [chromium] › editor/blocks/navigation-list-view.spec.js:86:2 › Navigation block - List view editing › list view should correctly reflect navigation items' structure [chromium] › editor/blocks/navigation-list-view.spec.js:137:2 › Navigation block - List view editing › can add new menu items [chromium] › editor/blocks/navigation-list-view.spec.js:253:2 › Navigation block - List view editing › can remove menu items [chromium] › editor/blocks/navigation-list-view.spec.js:297:2 › Navigation block - List view editing › can edit menu items [chromium] › editor/blocks/navigation-list-view.spec.js:385:2 › Navigation block - List view editing › can add submenus [chromium] › editor/blocks/navigation-list-view.spec.js:464:2 › Navigation block - List view editing › does not display link interface for blocks that have not just been inserted [chromium] › editor/blocks/navigation.spec.js:23:3 › Navigation block › As a user I want the navigation block to fallback to the best possible default › default to a list of pages if there are no menus [chromium] › editor/blocks/navigation.spec.js:49:3 › Navigation block › As a user I want the navigation block to fallback to the best possible default › default to my only existing menu [chromium] › editor/blocks/navigation.spec.js:91:3 › Navigation block › As a user I want the navigation block to fallback to the best possible