-
-
Notifications
You must be signed in to change notification settings - Fork 27
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
First stab at reverse hierarchical display (bug 106) #128
base: main
Are you sure you want to change the base?
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.
Just skimmed the review so far, might have a few more comments with more time, and will provide updated German translations.
On debugging, there is an option to disable popup auto-hide, then you should be able to switch windows in the inspector, then you should be able to get to the contents.
For CSS in the webcomponents you need to adjust the CSS within that .js file, for anything outside of the webcomponent it will be popup.css. This will also help you separate the visual from the data.
node = node.parent; | ||
} | ||
|
||
return parts; | ||
} | ||
|
||
get fullPathReversed() { |
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.
I think we should separate the display and data aspects. We can get the reversed parts with getFullNameParts(true).reverse()
, then in the folder nodes we can use templating and css to set the styles.
On the gmail and empty components thing, I think we could generally filter out empty components in getFullNameparts, and maybe add an option skipGmail that would then always skip [Gmail] folders.
while (node) { | ||
let isAcctNode = node instanceof AccountNode; | ||
if (includeAccountNode || !isAcctNode) { | ||
parts.unshift(node.item.name); | ||
} | ||
if (isAcctNode) { | ||
break; | ||
} | ||
node = node.parent; |
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.
while (node) { | |
let isAcctNode = node instanceof AccountNode; | |
if (includeAccountNode || !isAcctNode) { | |
parts.unshift(node.item.name); | |
} | |
if (isAcctNode) { | |
break; | |
} | |
node = node.parent; | |
while (node && (!(node instanceof AccountNode) || includeAccountNode)) { | |
parts.unshift(node.item.name); | |
node = node.parent; | |
} |
(untested)
I must be blind because I can't get the Inspector to show the pop up window. The Inspector for the add-on only shows the background page. |
Any ideas on this? |
Hey, sorry for the radio silence. Around that time I was prepping for a large event at work and then I missed picking this up again after. If you try the developer tools in the add-on options, there is an option to disable popup auto-hide. Can you try that one and see if it shows up? Otherwise, the main inspector in the toolbar, I'm not sure why it wouldn't show up. What it does is open another instance of Thunderbird and then connects the debugger. Can you try closing all other instances of Thunderbird maybe? Otherwise the folks in #maildev:mozilla.org on Matrix might be able to help you. |
I'm feeling stupid - can't get the inspector to show. Can you take a look and tell me what I'm doing wrong? https://www.loom.com/share/2a02d83666834a828f1acc1be8bcad92?sid=091156fa-1d5f-428f-b35b-08eeae660c05 |
You could try the full debugger that you can find in Tools > Developer Tools > Developer Toolbox. It will debug a lot more than the extension itself, but it is also more powerful. |
#106
Here is my first stab at this. Notes: