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

[Mobile] Sliding discussion item while dark mode is enabled causes b-color issue #1548

Closed
ardacebi opened this issue Aug 15, 2018 · 2 comments · Fixed by #2381
Closed

[Mobile] Sliding discussion item while dark mode is enabled causes b-color issue #1548

ardacebi opened this issue Aug 15, 2018 · 2 comments · Fixed by #2381

Comments

@ardacebi
Copy link
Contributor

ardacebi commented Aug 15, 2018

Bug Report

Current Behavior
Sliding a discussion item on the discussion list while dark mode is enabled causes the background color of the list to become white because of manual color setting (line 44):

https://github.com/flarum/core/blob/c16ddf24f2159c36e9026cb89457ec929a081fcc/less/forum/Slidable.less#L42-L48

Steps to Reproduce

  1. Enable Dark Mode
  2. Launch Flarum home screen on mobile
  3. Start sliding a discussion to reveal more button
  4. See error

Expected Behavior
Background color should stay something dark to match up with dark mode.

Screenshots

Environment

  • Flarum version: 0.1.0-beta.7
  • Website URL: localhost
  • Webserver: apache
  • Hosting environment: local
  • PHP version: 7.2.1
  • Browser: firefox quantum
@matteocontrini
Copy link
Contributor

Hello, this is still an issue.

Would it be a solution to use the @control-bg variable instead of the hardcoded white, as the Night Mode extension was doing?

https://github.com/FriendsOfFlarum/nightmode/blob/b972c5ffcd6875be3d98fdbb87a1856dfcd36334/resources/less/forum/extension.less#L490-L500

@askvortsov1
Copy link
Member

That definitely seems like a sensible solution! A PR would be welcome

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants