Maybe we should pass some kind of bool for "open this in a blank context" to the file handling code? That feels yucky, but OTOH it is clear that docshell cannot pass a browsing context that doesn't exist. I don't know what the best solution here is. It seems like here, the docshell code should be giving it a different browsing context for the _blank link, but presumably we don't want to do that for all external protocols because if they're not going to be handled in Firefox, what's the point - we would just open a blank tab for no reason at all. The web protocol handling code assumes that the target browsing context it gets given is correct. Under Choose Default Apps, select Email > Google Chrome. Edge: In Windows 10, go to Default App Settings. Enter mailto in search box and select result > Use Gmail > Use Gmail. The other pages where it doesn't work aren't in frames so we don't correct the target from within the web protocol handling code. Firefox: Go to menu > Options > General > Applications. It works because it's in a frame and because we refuse to open the link in the same (sub)frame. (In reply to Albert Scheiner from comment #39)įor some reason the target="_blank" seems to work on this pen: (I don't think the click or the mousedown on the iframe's html element have anything to do with it, but might be wrong).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |