Forum Discussion
AndreaBest
6 years agoQrew Trainee
For what its worth,
tldr: I changed the definition of the QuickBase button, unchecking the "open target in a new window", and now the button works for me.
Longer: Chrome version 76.0.3809.100 did change behavior. I didn't understand most of what the change talked about. It did cover issues regarding opening a new window, copying context, and queueing up clicks. Chrome folks said the changed behavior is the correct behavior, and will not be changing it back. For my application, I did not need or want a new window opened. I was surprised to see the checkbox for my button filled in to open a new window. It was worth experimenting to remove the check, and looks like that solved the problem for me.
Good luck all, hope you find solutions that fit your applications.
tldr: I changed the definition of the QuickBase button, unchecking the "open target in a new window", and now the button works for me.
Longer: Chrome version 76.0.3809.100 did change behavior. I didn't understand most of what the change talked about. It did cover issues regarding opening a new window, copying context, and queueing up clicks. Chrome folks said the changed behavior is the correct behavior, and will not be changing it back. For my application, I did not need or want a new window opened. I was surprised to see the checkbox for my button filled in to open a new window. It was worth experimenting to remove the check, and looks like that solved the problem for me.
Good luck all, hope you find solutions that fit your applications.