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

A rainbow frame demo doesn't work in ladybird #2705

Open
1 task
shlyakpavel opened this issue Dec 2, 2024 · 3 comments
Open
1 task

A rainbow frame demo doesn't work in ladybird #2705

shlyakpavel opened this issue Dec 2, 2024 · 3 comments

Comments

@shlyakpavel
Copy link
Contributor

Summary

When I open rainbow frame demo in Ladybird, it doesn't work

Operating system

macOS

Steps to reproduce

  1. Open Ladybird
  2. Navigate to http://menlodyand.temp.swtest.ru/pages/rainbow/
  3. Observe

Expected behavior

Picture has a frame that shines

Actual behavior

There's no frame

URL for a reduced test case

http://menlodyand.temp.swtest.ru/pages/rainbow/

HTML/SVG/etc. source for a reduced test case

N/A

Log output and (if possible) backtrace

N/A

Screenshots or screen recordings

image image

Build flags or config settings

No response

Contribute a patch?

  • I’ll contribute a patch for this myself.
@AtkinsSJ
Copy link
Member

AtkinsSJ commented Dec 2, 2024

That's doing quite a few things... But I think the biggest is that we don't support border-image at all, so even if everything else worked, the rainbow border wouldn't show!

Other potential problems:

  • Custom property used inside a gradient description
  • Animating a custom property
  • Using @property (not sure if this actually makes a difference)

Side note: Using vendor-prefixes and @property in the same code feels weirdly anachronistic. 😆

@shlyakpavel
Copy link
Contributor Author

@AtkinsSJ vendor-prefixes have been removed ;^)

@Menlod
Copy link

Menlod commented Dec 2, 2024

Side note: Using vendor-prefixes and @Property in the same code feels weirdly anachronistic. 😆
Is's

It was a regular PostCSS autoprefixer.
Without it, as I see, the result did not change.

All your assumptions for the error are valid. I am not a browser developer. I am not trying to offend you in any way.

I am just showing what exactly does not work.

Thank you very much for your work.

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

3 participants