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.

Sign up for GitHub

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

Jump to bottom

Buttons using is-<info/success/warning/danger> and disabled are white in Safari 15.4 #3515

Closed
sysophost opened this issue Apr 27, 2022 · 3 comments
Closed

Buttons using is-<info/success/warning/danger> and disabled are white in Safari 15.4 #3515

sysophost opened this issue Apr 27, 2022 · 3 comments

Comments

@sysophost
Copy link

sysophost commented Apr 27, 2022 •
edited
Loading

Overview of the problem

This is about the Bulma CSS framework
I'm using Bulma version 0.9.3
My browser is: Safari 15.4

Description

Buttons that use the disabled attribute, in conjunction with is-info/is-success/is-warning/is-danger class are white (so invisible on a white background) but respond correctly when hovered.

Adding an additional class, such as is-light/is-inverted or removing the is-success class results in the disabled button being displayed as expected.

Steps to Reproduce

  1. Create a page with a disabled button.

    <html>
<head>
    <link rel="stylesheet" href="./bulma/css/bulma.css">
</head>
<body>
    <button class="button is-success" disabled>Disabled button</button>
    <button class="button is-success">Enabled button</button>
</body>
<html>

  2. Render page in Safari

  3. Observe disabled button is rendered in white

Expected behavior

Buttons using the disabled attribute, in conjunction with is-success class, should be rendered with the correct colouring but disabled

Actual behavior

Buttons using the disabled attribute, in conjunction with is-success class, are white (so invisible on a white background)
@sysophost
Copy link
Author

sysophost commented Apr 27, 2022 •
edited
Loading

This previously was not an issue so is presumably related to a change in the latest version of Safari on macOS 12.3.1.

@nabedge
Copy link

nabedge commented May 2, 2022

It is probably same issue for #3500

@jgthms
Copy link
Owner

jgthms commented May 7, 2022

Duplicate of #3500. Working on it now.

@jgthms jgthms closed this as completed May 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jgthms @nabedge @sysophost