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

Inline span collapses to width 0 on Firefox when Stega is enabled in Sanity #8464

Open
giacomoalonzi opened this issue Jan 31, 2025 · 0 comments

Comments

@giacomoalonzi
Copy link

If you find a security vulnerability, do NOT open an issue. Email [email protected] instead.

Describe the bug
When Stega is enabled in Sanity, inline span elements in the front-end collapse with a width of 0, making their content invisible. This issue occurs primarily on Firefox and seems to be related to Stega’s injected code. Disabling Stega prevents the problem from happening. I’ve mainly observed this behavior with span elements.

To Reproduce

Steps to reproduce the behavior:

  1. Enable Stega in Sanity Studio.
  2. Use an inline span with text content in the front-end.
  3. Open the page in Firefox.
  4. Notice that the span collapses with a width of 0.

Expected behavior

The span should display its content normally without collapsing its width, even with Stega enabled.

Screenshots
If applicable, add screenshots to help explain your problem.

Image
Stega Enabled

Image
Stega diabled

Which versions of Sanity are you using?

3.72.1

What operating system are you using?
macOS 15.3

Which versions of Node.js / npm are you running?

npm: 10.8.3
node: v22.9.0

Additional context

Add any other context about the problem here.

Security issue?

Any security issues should be submitted directly to [email protected]. In order to determine whether you are dealing with a security issue, ask yourself these two questions:

  • Can I access something that's not mine, or something I shouldn't have access to?
  • Can I disable something for other people? If the answer to either of those two questions are "yes", then you're probably dealing with a security issue. Note that even if you answer "no" to both questions, you may still be dealing with a security issue, so if you're unsure, just email us at [[email protected]](mailto:[email protected].
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant