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

Word Break inconsistency between Chrome and Firefox #19

Closed
ghost opened this issue Apr 10, 2021 · 7 comments
Closed

Word Break inconsistency between Chrome and Firefox #19

ghost opened this issue Apr 10, 2021 · 7 comments
Assignees

Comments

@ghost
Copy link

ghost commented Apr 10, 2021

Is your feature request related to a problem? Please describe.
Chrome doesn't wrap its links at all while Firefox does.
Chrome uses a different default value for word-break then Firefox as after adding word-break: break-word; on its links it behaved the same way as Firefox did.
I also saw that similar questions have come up before and they were put aside because of "unexpected behaviors", but this seems like a special case as it to only happens with the tag so it could be an exception.

Describe the solution you'd like

a {
  cursor: pointer;
  color: #3333e1;
  background-color: transparent;
  text-decoration: none;
  word-break: normal;
}

Additional context
Originally Opened By @Gaboris at necolas/normalize.css#851 Plus, Original Solution By @VixieTSQ in necolas/normalize.css#852

@ghost ghost added enhancement labels Apr 10, 2021
@ghost
Copy link
Author

ghost commented Apr 10, 2021

Waiting For Some One To Grab This Good First Issue! Well if anyone is interested kindly comment here (I'll Assign It You And Only You)

@VixieTSQ
Copy link
Contributor

Waiting For Some One To Grab This Good First Issue! Well if anyone is interested kindly comment here (I'll Assign It You And Only You)

I already made a pull request. So... why give it off to someone else?

@ghost
Copy link
Author

ghost commented Apr 10, 2021

@VixieTSQ We are fixing the issues of other related projects to make reseter.css perfect. You made a pull request to normalize.css repo the code is different in reseter.css and normalize.css. The Things Remain The Same But Repositories And Files And Sources Change. So it means that we can't merge the pull request from the normalize.css repo to this repo. If you want you can submit a pull request here as well. But You Were The Original Person To Solve It. You Deserve Appreciation Thus Our All Contributors Bot Will Add You To The Contributors List. :)

@allcontributors
Copy link
Contributor

@krishdevdb

I've put up a pull request to add @VixieTSQ! 🎉

@VixieTSQ
Copy link
Contributor

@VixieTSQ We are fixing the issues of other related projects to make reseter.css perfect. You made a pull request to normalize.css repo the code is different in reseter.css and normalize.css. The Things Remain The Same But Repositories And Files And Sources Change. So it means that we can't merge the pull request from the normalize.css repo to this repo. If you want you can submit a pull request here as well. But You Were The Original Person To Solve It. You Deserve Appreciation Thus Our All Contributors Bot Will Add You To The Contributors List. :)

Oh sorry, sorry when I got this notification I thought it was on the normalize.css repository. Nevermind

@ghost
Copy link
Author

ghost commented Apr 12, 2021

No Problem @VixieTSQ

@ghost
Copy link
Author

ghost commented Apr 19, 2021

Fixed In #30

@ghost ghost closed this as completed Apr 19, 2021
@ghost ghost mentioned this issue May 1, 2021
@ghost ghost pinned this issue May 1, 2021
@ghost ghost unpinned this issue May 1, 2021
@ghost ghost added code labels Jun 18, 2021
@ghost ghost assigned VixieTSQ Jun 18, 2021
This issue was closed.
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