Skip to content
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.

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

Charts not visible inside Tabs #1072

Closed
AndreeaCristinaRadacina opened this issue Jan 21, 2024 · 1 comment · Fixed by #1074 or #1077
Closed

Charts not visible inside Tabs #1072

AndreeaCristinaRadacina opened this issue Jan 21, 2024 · 1 comment · Fixed by #1074 or #1077
Assignees
Labels
bug This label could be used to identify issues that are caused by a defect in the product. customer report Indicates the request came from a customer. Priority-Medium Expected resolution time - up to 1 month. released Indicate that an issue has been resolved and released in a particular version of the product. small (1-3h) This label is used for issues that can be completed within 3 hours or less.

Comments

@AndreeaCristinaRadacina

Description

A user reported that charts are not visible inside the tabs, even if their actions (Print, Edit) can be seen.

Ref: https://wordpress.org/support/topic/charts-no-longer-load-except-for-front-end-actions-links/#post-17357169

I managed to replicate this for both Tabby (the plugin he uses) and Otter Blocks (Tabs block)

Step-by-step reproduction instructions

  1. Install Tabby Responsive Tabs
  2. Copy this code and paste it on a page:
[tabby title="First Tab"]

This is the content of the first tab.

[tabby title="Second Tab"]

This is the content of the second tab.
[tabby title="Third Tab"]

This is the content of the third tab.

[tabbyending]
  1. Insert one of the Visualizer's shortcodes inside one of the tabs.
  2. Publish and check the page

Do the same for Otter:

  1. Add the Tabs block
  2. Inside one of the tabs, insert a chart's shortcode

Screenshots, screen recording, code snippet or Help Scout ticket

Screenshot 2024-01-21 at 12 43 43

Environment info

No response

Is the issue you are reporting a regression

No

@AndreeaCristinaRadacina AndreeaCristinaRadacina added the bug This label could be used to identify issues that are caused by a defect in the product. label Jan 21, 2024
@pirate-bot pirate-bot added the customer report Indicates the request came from a customer. label Jan 21, 2024
@vytisbulkevicius vytisbulkevicius added the Priority-Medium Expected resolution time - up to 1 month. label Jan 22, 2024
@Soare-Robert-Daniel Soare-Robert-Daniel added the small (1-3h) This label is used for issues that can be completed within 3 hours or less. label Jan 23, 2024
@vytisbulkevicius vytisbulkevicius linked a pull request Feb 6, 2024 that will close this issue
@pirate-bot
Copy link
Contributor

🎉 This issue has been resolved in version 3.10.7 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@pirate-bot pirate-bot added the released Indicate that an issue has been resolved and released in a particular version of the product. label Feb 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This label could be used to identify issues that are caused by a defect in the product. customer report Indicates the request came from a customer. Priority-Medium Expected resolution time - up to 1 month. released Indicate that an issue has been resolved and released in a particular version of the product. small (1-3h) This label is used for issues that can be completed within 3 hours or less.
Projects
None yet
4 participants