I tried! It seems that browsers force an extension to put all of itās things into one item. It kind of makes sense, otherwise the context menu could get real long. I mean, wouldnāt every extension maker want all of their features top level? Iāll keep asking around. I think if only one was enabled then it goes to the top level. So remind me to add a setting to disable them one by one, and that might fix it. And of course you could extract that feature into itās own extension. The framework Iām using makes this super easy.
Yeah, this has to do with detecting the element being hovered over. To detect parents all the way up till you get to an <a> tag might be a drag on performance. Remember, with this feature it is listening for every element that you hover over on every web page you visit. I canāt remember if there is already debouncing going on or not.
It seems that in HTML5 itās legal to wrap a block level element with a tags even though a tags are line level. ĀÆ\_(ć)_/ĀÆ
It may not be able to support blurbs in every single instance. For example on Mastodon it appears that the way links are shortened for display purposes also messes with this feature.
BTW, I have disabled this feature on the CIPS because pop up blurbs are native to the app. If there are other sites where the blurbs are problematic I can hard disable them. Once there are settings users could also disable specific sites I guess.













