Customer Reports
3168571-zen
3204865-zen
23345765-hc
3168571-zen
Steps to replicate
It does work on some browsers for some users. For example, this is what I see on Firefox:
Dismissing the notice on firefox while logged in as the same user will ensure that the issue is fixed the next time I access the order edit page in Chrome.
Here are my browser details:
Chrome (bug): https://www.whatsmybrowser.org/b/41D1T
Firefox (works fine): https://www.whatsmybrowser.org/b/HI6DL
However, user in 3168571-zen reported that none of the browsers worked for them:
https://www.whatsmybrowser.org/b/ZK5RL
https://www.whatsmybrowser.org/b/5SEC9
https://www.whatsmybrowser.org/b/V6Y18
Expected Behavior
Either fix the problem with pop-up hiding other options on some browsers or make it a notification like other WordPress notifications and not a pop-up.
Marking as high priority because without reaching out to support or performing a complete conflict test, most users wouldn't know what exactly is happening.
Previous slack discussion: p1593417215220200-slack-fulfill-support
Edit: In my case, I could not replicate the behavior on my Macbook. The problem could only be replicated on iMac.
reported in 3204865-zen as well
From the original bug report:
However, user in 3168571-zen reported that none of the browsers worked for them
User in 3204865-zen also reports that neither Firefox nor Chrome is working for them and shared the following screencast: https://www.loom.com/share/d52b86e11f124ff080dc9876c8b68a67
Considering that this breaks order management entirely, I'm bumping to critical.
Hi,
I took a look at this and I could not reproduce the problem on both local environment and live environment, against both Chrome (latest 84) and FIrefox (latest 79).
I can see both showing:

I am wondering if these are caching issues on their host providers. Were you able to reproduce this on a fresh installation?
Thank you for checking, @harriswong
Were you able to reproduce this on a fresh installation?
Yep. The screenshots on the original report are from my own test sites. Heads up that it could also be due to the screen size (updating original report).
While I did have the problem in iMac, that wasn't the case using a laptop.
Just had a instance of this in 23345765-hc
I was able to reproduce it on their site using Chrome too. Currently, plugin is disabled.
Thanks for the reports! I believe I have a fix (for what I believe is the cause of the issue) ready in https://github.com/Automattic/woocommerce-services/pull/2139 - feel free to check out the changes there
Thank you for the PR @frosso.
I downloaded the PR as a zip file, but I'm still seeing the same behavior on my own test site. Here's the file I downloaded https://d.pr/f/g966yj
@AashikP thanks for testing it out! In order to check out the changes, you'll need a compiled version of the plugin. I created one for you: https://d.pr/f/x3YDhN
Let me know if this works better!
you'll need a compiled version of the plugin.
Thank you for reminding me @frosso 🤦🏻♂️
While the compiled version did not work initially, I _could get it to work while logged in via incognito_. Probably caching. So yeah, the fix indeed seems to work :)
@AashikP Thanks again for taking the time to test it!!
Also reported in 3237565-zen
Here the problem only happened when Shipping Labels were disabled under WooCommerce > Settings > Shipping > WooCommerce Services. Enabling them back works as a temporary workaround:
Screenshot: https://d.pr/i/AW5L5n
Got another one in 3237565-zen, and added it and the rest to the top of the report.
I tried to update using the compiled version above, but it didn't install, most likely because it's an AT site on WP.com.
Image Link: https://d.pr/i/EeaPBG
@madeincosmos replied as I was replying, so I went off of what she said and toggled the Shipping Labels off and on again and that seems to have corrected the issue for now.
_Edit: Somehow Maria and I were on the same ticket, so it may be she fixed it before I did 🤷 _
Most helpful comment
Thank you for reminding me @frosso 🤦🏻♂️
While the compiled version did not work initially, I _could get it to work while logged in via incognito_. Probably caching. So yeah, the fix indeed seems to work :)