From: josecss.es@gmail.com   
      
   El 13/12/2025 a las 21:29, Jota.Ce escribió:   
   > El 13/12/2025 a las 12:15, Nuno Silva (testing) escribió:   
   >> Nuno Silva wrote:   
   >>> On 2025-11-27, Jota.Ce wrote:   
   >>>   
   >>>> El 25/11/2025 a las 11:32, Daniel70 escribió:   
   >>>>> On 25/11/2025 6:06 am, Jota.Ce wrote:   
   >>> [...]   
   >>>>>> I can't do anything in that OAuth2 popup window with context menu,   
   >>>>>> shortchut keys, address bar,... just only clicking and writing on   
   >>>>>> form's text boxes, and clicking on form's buttons.   
   >>>>>>   
   >>>>>> Is there maybe a setting in about:config to allow any other actions?   
   >>>>> I would think 'YES' .... but what they are is beyond me. Sorry.   
   >>>> Does anyone know how to avoid that a form or a popup window forbids   
   >>>> using context menu or shortcuts?   
   >>>>   
   >>>> I mean... a form could forbit those actions through JavaScript,   
   >>>> but... why can't you just simply hit F5 on that popup window?   
   >>>   
   >>> It probably is about either how the window includes the web page area,   
   >>> or about how the window is opened.   
   >>>   
   >>> My guess is that currently, even without controls, it'll be possible to   
   >>> come up with a hack using the Browser Console.   
   >>   
   >> *Possible* yes, albeit quick and dirty. And from a not-so-caffeinated brain:   
   >>   
   >> {let e = Services.wm.getEnumerator(""); while (e.hasMoreElements()) { let w   
   = e.getNext(); if (w.document.documentURI ==   
   >> "chrome://messenger/content/browserRequest.xul") {console.log("Window   
   found, reloading content frame");   
   >> w.document.getElementById("requestFrame").reload(); break;}}}   
   >>   
   >> (I wrote that in one line to avoid having to deal with newlines in the   
   browser console when copy-pasting this, but it's going to get wrapped   
   >> in this post anyway :-) )   
   >>   
   >> (That ought to loop through windows*, and, if the Mail&News'    
   rowserRequest.xul window is found, reloads its content. If more than one such   
   >> window exists, only the first gets reloaded ("break;").)   
   >>   
   >> * (I have to check if "" does the same as null or not, but it does get the   
   OAuth2 request window, so that's OK here; that window does not seem   
   >> to have a type, so specifying one won't work here?)   
   >>   
   >> This code would go in the prompt in the Browser Console window (reachable   
   from a Navigator window: Tools->Web Development->Browser Console, or   
   >> Ctrl+Shift+J, at least on Windows and Linux). My notes say this needs the   
   chrome.devtools.enabled preference to be set to true (otherwise   
   >> there will be no such prompt in the Browser Console).)   
   >>   
   >>   
   > Hi.   
   >   
   > Before anything, thanks a lot for your time and your knowledge.   
   >   
   > Excuse me, but Browser console is read-only here.   
   >   
   > I have set chrome.devtools.enabled to true, but i think i can't see any   
   difference from before: Browser console only shows some errors, but it   
   > doesn't let me write anything.   
   OK, the exact setting is devtools.chrome.enabled and then you get the prompt   
   line.   
      
   I'll try to go on.   
      
   Thanks, by the way.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)