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

fix(Input): icon should be always after <input> #2302

Merged
merged 1 commit into from
Nov 16, 2017
Merged

Conversation

layershifter
Copy link
Member

Fixes #2298.

@codecov-io
Copy link

Codecov Report

Merging #2302 into master will decrease coverage by <.01%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #2302      +/-   ##
==========================================
- Coverage   99.73%   99.73%   -0.01%     
==========================================
  Files         152      152              
  Lines        2656     2655       -1     
==========================================
- Hits         2649     2648       -1     
  Misses          7        7
Impacted Files Coverage Δ
src/elements/Input/Input.js 100% <ø> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6ef5af5...379ef64. Read the comment docs.

@layershifter
Copy link
Member Author

@levithomason I don't merge this because I don't remember the reasons for different positions. Can you clarify?

@levithomason
Copy link
Member

The change of position here was strictly for HTML correctness with the prop value (left). However, it appears the CSS rule was overlooked. Your change is acceptable.

Someday, inline styles will remove all this CSS hierarchy dependency. Long live that day!

@levithomason levithomason merged commit 21ebc89 into master Nov 16, 2017
@levithomason levithomason deleted the fix/input-icon branch November 16, 2017 23:01
@levithomason
Copy link
Member

Released in semantic-ui-react@0.77.0

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

Successfully merging this pull request may close these issues.

3 participants