Skip to content
This repository has been archived by the owner on Feb 23, 2024. It is now read-only.

Incompatible plugin declaration message not displaying correctly in Safari #11734

Closed
grenadeco opened this issue Nov 10, 2023 · 2 comments · Fixed by #11736
Closed

Incompatible plugin declaration message not displaying correctly in Safari #11734

grenadeco opened this issue Nov 10, 2023 · 2 comments · Fixed by #11736
Assignees
Labels
priority: high The issue/PR is high priority—it affects lots of customers substantially, but not critically. type: bug The issue/PR concerns a confirmed bug. type: community contribution

Comments

@grenadeco
Copy link

Describe the bug

While testing the Checkout Block incompatible plugin declaration message, I noticed the message displayed as blank in Safari.

To reproduce

Steps to reproduce the behavior:

  1. Install WooCommerce
  2. Instal a WooCommerce plugin that is not yet compatible with the new Checkout Blocks and has declared incompatibility (e.g. Checkout Field Editor).
  3. Navigate to the Checkout page
  4. Select a block and view the Block option panel on the right of the screen
  5. The plugin declaration message area displays, however, the actual message is blank.

Expected behavior

The plugin declaration message should display as expected.

Screenshots

Safari:
Screenshot 2023-11-10 at 14 19 48

Expected behavior (Chrome):
Screenshot 2023-11-10 at 14 26 38

Environment

WordPress (please complete the following information):

  • WordPress version: 6.4.1
  • Gutenberg version (if installed): NA
  • WooCommerce version: 8.3.0-rc.2
  • WooCommerce Blocks version: NA
  • Site language: English (United States)
  • Any other plugins installed: WooCommerce Checkout Field Editor 1.7.12

Desktop (please complete the following information):

  • OS: macOS
  • Browser: Safari
  • Version: 16.3

Smartphone (please complete the following information):

NA

Additional context

None

@grenadeco grenadeco added the type: bug The issue/PR concerns a confirmed bug. label Nov 10, 2023
@ralucaStan ralucaStan added the priority: high The issue/PR is high priority—it affects lots of customers substantially, but not critically. label Nov 10, 2023
@ralucaStan
Copy link
Contributor

Thank you @grenadeco for this report. I was able to replicate

@nielslange
Copy link
Member

Hello @grenadeco 👋

Thanks for reaching out and congratulations for your very first bug report! 👏 Similar to @ralucaStan, I was able to reproduce this issue and I went ahead and fixed it in #11736. Usually, reports did not get addressed that fast, but you discovered a critical bug. Thanks again for reporting it! 🙌

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
priority: high The issue/PR is high priority—it affects lots of customers substantially, but not critically. type: bug The issue/PR concerns a confirmed bug. type: community contribution
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants