8000 Context menus for blocks in flyouts remain open when the flyout closes · Issue #8791 · google/blockly · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Context menus for blocks in flyouts remain open when the flyout closes #8791

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.

Sign up for GitHub

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

Jump to bottom
Closed
1 task done
microbit-robert opened this issue Mar 6, 2025 · 2 comments
Closed
1 task done

Context menus for blocks in flyouts remain open when the flyout closes #8791

microbit-robert opened this issue Mar 6, 2025 · 2 comments
Assignees
@RoboErikG
Labels
issue: bug Describes why the code or behaviour is wrong

Comments

@microbit-robert
Copy link
Contributor

Check for duplicates

  • I have searched for similar issues before opening a new one.

Description

If you right click on a block in a flyout, the context menu opens. If you then click on the main workspace, the flyout closes, but the context menu for the block that was in the flyout remains open. You can only close this context menu by interacting with it, or opening another context menu.

Reproduction steps

  1. Open Blockly playground page
  2. Click on the "Logic" category
  3. Right click on the "if... do..." block to open a context menu
  4. Click on the main workspace
  5. Observe that the flyout closes but the context menu remains open

Stack trace



Screenshots


Image


Browsers


Chrome desktop

      		
    

      
  





        



            
            

              
            

        

      


      
    








      

    



      

  
            

    

      
    

    


      

          @microbit-robert
microbit-robert




            added
      

  issue: bug

  Describes why the code or behaviour is wrong

      

  issue: triage

  Issues awaiting triage by a Blockly team member

  labels


      Mar 6, 2025

    

  



    

    

      
    

    


      

          @cpcallen
cpcallen




          removed
  the 

  issue: triage

  Issues awaiting triage by a Blockly team member
 label


      Mar 7, 2025

    

  



    


    







      

  
      



  

  @cpcallen





  


    

      

  

    

        
    
    

  


      
          
  
      
            Copy link

  

      
    

  


  

      

  
    Contributor


      

  


  
    

      

      
            cpcallen
  

      

      

      commented


        Mar 7, 2025


      
  •

  

    
      

        
          edited
          
        
        
      

    
    
      
  
        
      Loading


  
    
  



    


  




      


        


  
    

      
          
See also google/blockly-keyboard-experimentation#276 and #8615.

      		
    

  





        


            

            
            

              
            

        

      


      

            
  
  

    
  
    
    

  

  

  


    












      

  
      



  

  @RoboErikG





  


    

      

  

    

        
    
    

  


      
          
  
      
            Copy link

  

      
    

  


  

      

  
    Contributor


      

  


  
    

      

      
            RoboErikG
  

      

      

      commented


        Mar 7, 2025


      
  •

  

    
      

        
          edited
          
        
        
      

    
    
      
  
        
      Loading


  
    
  



    


  




      


        


  
    

      
          
It looks like this was fixed by #8600 and is no longer reproducible in develop. The Playground is still using v11.1.1 which is 8 months out of date and doesn't include the fix.


Please let me know if you find a case where this is still an issue on develop.

      		
    

  





        


            

            
            

              
            

        

      


      

            
  
  

    
  
    
    

  

  

  


    












      

  
            

    











  
  

    

      

  





  




  
  

              

  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment


  



  






  
                    




    

  


      
  

    Assignees
  



        

      

        

  
      @RoboErikG
  
    RoboErikG
    

      








      


  


  

    Labels
  



    

      

    issue: bug

  Describes why the code or behaviour is wrong








      

  

    

        

    Projects
  


        




        
  

    

      
          
        Blockly Q1 2025
        
    

    

      

            
    Status: No status

              
      

    

    

  







  



      


  

    
  

    Milestone
  


      No milestone





    
      
          


  

    

      
        

          
    

    Development
  




            
    
No branches or pull requests







      
    

  




      

    

  
      

  

    

      3 participants
    

    

        
          @cpcallen 
        
          @RoboErikG 
        
          @microbit-robert 
    

  






    

    




    






  

          

        



    



  





    

  


  


          



    



  

    

    

    





    


    

    

  



0