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 heading bug in Style.css #309

Merged
merged 1 commit into from Dec 10, 2018
Merged

Conversation

yh54321
Copy link
Contributor

@yh54321 yh54321 commented Dec 9, 2018

Fixes bug which causes certain chapter titles to be stylized incorrectly
(Compare chapter 2 to chapter 3: https://s3.amazonaws.com/moby-dick/moby-dick.epub)
Affects span elements within h1-6 elements

Fixes bug which causes certain chapter titles to be stylized incorrectly.
(Compare chapter 2 to chapter 3: https://s3.amazonaws.com/moby-dick/moby-dick.epub)
Affects <span> elements within <h1-6> elements
@mahavir155 mahavir155 merged commit 7de3372 into FolioReader:master Dec 10, 2018
@mahavir155
Copy link
Contributor

thanks @yh54321

hrishikesh-kadam added a commit to codetoart/FolioReader-Android that referenced this pull request Dec 10, 2018
@yh54321 yh54321 deleted the patch-1 branch December 10, 2018 08:50
@yh54321 yh54321 restored the patch-1 branch December 14, 2018 07:41
@yh54321 yh54321 deleted the patch-1 branch December 14, 2018 07:43
@yh54321
Copy link
Contributor Author

yh54321 commented Dec 14, 2018

I found an error in my fix, it won't work.
Best thing is to revert and delete line 301 like @hrishikesh-kadam did in his repo, (unless line 301 has a purpose...), or to accept another PR I'm about to post.

yh54321 added a commit to yh54321/FolioReader-Android that referenced this pull request Dec 14, 2018
Patches problem in fix PR FolioReader#309.
Another solution is to revert FolioReader#309 and to delete line 301 (if it is not needed).
@hrishikesh-kadam
Copy link
Contributor

hrishikesh-kadam commented Dec 14, 2018

@yh54321 Yes, exactly. Changes in codetoart@07bee5a would be sufficient.
Don't worry about breaking master branch as changes in above commit will get merge in FolioReader master for next release.

@mahavir155 We can close PR #313

@yh54321
Copy link
Contributor Author

yh54321 commented Dec 14, 2018

@hrishikesh-kadam Okay, thank you

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

Successfully merging this pull request may close these issues.

None yet

3 participants