Skip to content

[$20] - Challenge details page hyperlink (Hover, normal, visited) colors are wrong #220

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

Closed
sdgun opened this issue Aug 24, 2017 · 5 comments

Comments

@sdgun
Copy link
Collaborator

sdgun commented Aug 24, 2017

Steps to Reproduce

Actual Result(s)

  • Challenge details page hyperlink (Hover, normal, visited) colors are wrong

Expected Result(s)

  • Must match with the style guide, attached

Environment

  • Device(s): Laptop
  • Operating System: Windows 7 64bit
  • Browser(s): Chrome 60.0.3112.101 (Official Build) (64-bit)

Image/Video/JS Log/Console Log (If not attached here, Please check the comments section)

@sdgun
Copy link
Collaborator Author

sdgun commented Aug 24, 2017

23

23 1

@birdofpreyru birdofpreyru changed the title Challenge details page hyperlink (Hover, normal, visited) colors are wrong [$10] - Challenge details page hyperlink (Hover, normal, visited) colors are wrong Aug 24, 2017
@birdofpreyru birdofpreyru changed the title [$10] - Challenge details page hyperlink (Hover, normal, visited) colors are wrong [$20] - Challenge details page hyperlink (Hover, normal, visited) colors are wrong Aug 24, 2017
@birdofpreyru
Copy link
Collaborator

Accepted, 1 point

@iversonLv
Copy link
Contributor

For this page, spec content is written from Editor which has inline css, seems can't not fix via css file?

@birdofpreyru
Copy link
Collaborator

Well, we don't touch those styles that have been explicitely set as inline styles by the editor. However, on this page it is not always the case. E.g. the first blue link becomes dark gray on hover, however I don't see any inline styling for this in the page source.

twicoder pushed a commit that referenced this issue Aug 25, 2017
@twicoder
Copy link

PR #301

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

5 participants