-
Notifications
You must be signed in to change notification settings - Fork 999
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WIP] Porting Masthead to Vue.js #9071
Conversation
Thank you so much for working on this. I noticed that there is an issue with the navigation, an error is triggered when navigating to the admin panel and then back to the workflow list. I also noticed that the masthead is not rendered for the data libraries view. |
@guerler, thank you for checking it! I am going to try to fix the issues you've noticed tomorrow. |
I assume you are referring to |
Implement hidden tabs also to match unit tests in qunit.
I tried to transfer a bunch of the tests - got everything transferred except some of the scratchbook interaction tests. I think they didn't work because I'm modeling the tab definitions with a POJO in the test instead of a Backbone collection. I think that probably represents the direction we want to go but if you'd like me to redo the test setup with a Backbone collection and get those last few assertions I can do that otherwise, I'll remove the qunit tests. Hopefully whoever ports scratchbook.js to VueJS covers that remaining functionality with a unit test - also I think we have Selenium coverage for this because we run through the scratchbook tour. I'll try working on figuring out the Selenium failures and cleaning up the unneeded code (if any) now. |
Problem is the interactive tooltips that are off by default in bootstrap but not bootstrap-vue. interactive tooltips are better for accessibility though so best to just work around them for testing?
v-b-popover.manual.bottom="{ id: tab.id, content: popoverNote, html: true }" | ||
@click="open(tab, $event)" | ||
> | ||
<template v-if="tab.icon"> |
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.
It'd be great if future work could keep in mind and use the new(ish) vue-fontawesome work that was introduced to swap out the old style fontawesome classes and includes.
user: | ||
type: xpath | ||
selector: '//li[@id="user"]' | ||
# bootstrap-vue a tag doesn't work as link target, need to hit span inside |
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.
Hopefully this doesn't break many tours.
It looks like dropdown doesn't close on mouse click (click on outer area of dropdown div). Update: |
@OlegZharkov What browser? Anything weird in the console? It seems to work for me. (FF-DeveloperEdition) |
@dannon |
@OlegZharkov I think it's that you're clicking inside the welcome iframe on (https://stackoverflow.com/questions/11351726/bootstrap-dropdown-doesnt-collapse-when-clicking-over-iframe -- the blur idea looks reasonable to me) |
@dannon |
@OlegZharkov Just saw the ping here, too. Feel free to take this over: https://github.com/galaxyproject/galaxy/compare/dev...dannon:fix-iframe-menuhide?expand=1 |
A big difference is interactive being on by default for the bootstrap-vue but not for bootstrap. So the menu is more persistent now. This is an accessibility thing - https://bootstrap-vue.org/docs/components/tooltip. I don't know if the blur thing is equivalent to just swapping that but something to consider, I didn't know about the option before looking into why the test behavior changed. 387fded Update: I guess that was tooltips - not menus. Yeah ignore this. |
This is a work in progress on porting the masthead to Vue.js.