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

BakaTsuki - Content list (table of contents) #27

Closed
typhoon71 opened this issue Jun 28, 2016 · 26 comments
Closed

BakaTsuki - Content list (table of contents) #27

typhoon71 opened this issue Jun 28, 2016 · 26 comments

Comments

@typhoon71
Copy link

Small fix needed.
If the table of content is hidden while viewing a BakaTsuki novel, the plugin will show a page like this.

ee

Can an option be added to remove it completely if it's hidden?
And maybe another option to automaticlly "show" it instead?

@belldandu
Copy link
Contributor

Toc is actually stripped from the novel

// discard table of contents (will generate one from tags later)

The problem here is that the class changes to "toc tochidden" when you click hide. Which causes it to remain.

simple fix would be to compare the id instead of the class. @dteviot

@belldandu
Copy link
Contributor

@typhoon71 can this be closed?

@typhoon71
Copy link
Author

Uhm, I don't see any difference from 0.0.0.7? Did the "simple fix" above get implemented?
If it won't, I'm fine closing this anyway because I just need to not hide the toc on the novel page.

@dteviot
Copy link
Owner

dteviot commented Jun 29, 2016

@typhoon71
It should have been.
The code change has been committed.
d401703,
lines 119 - 120.
That said, fix looked so simple I did not test it.
And it's always possible I sent the wrong file to Google.

On Thu, Jun 30, 2016 at 5:52 AM, typhoon71 notifications@github.com wrote:

Uhm, I don't see any difference from 0.0.0.7? Did the "simple fix" above
get implemented?
If it won't, I'm fine closing this anyway because I just need to not hide
the toc on the novel page.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#27 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AE6w2YJOgugVgKxN5OkbsIVSHIQgEqHGks5qQrDfgaJpZM4I_yW2
.

@typhoon71
Copy link
Author

OK, I'm testing v0009 from sonako with firefox (oogle still on v0008).
I get this with every novel I try.

ufff

Happens with "Set Cover" both selected or unselected.

@dteviot
Copy link
Owner

dteviot commented Jun 29, 2016

@typhoon71
I will have to look into this tonight. Currently busy at my day job.

I'll point out v0.0.0.9 is just because I bump the version number
immediately after a release. Code wise, 0.0.0.9 from sonako branch is same
as the 0.0.0.8 release.

On Thu, Jun 30, 2016 at 8:23 AM, typhoon71 notifications@github.com wrote:

OK, I'm testing v0009 from sonako with firefox (oogle still on v0008).
I get this with every novel I try.

[image: ufff]
https://cloud.githubusercontent.com/assets/1866248/16467504/f0577c64-3e47-11e6-83d9-3108e7eac1eb.png

Happens with "Set Cover" both selected or unselected.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#27 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AE6w2SLvdALQMIbZVaPdNus9F-Di-jZsks5qQtRTgaJpZM4I_yW2
.

@typhoon71
Copy link
Author

np, do it when you can/want, I'm already happy I won't have to do the html -> epub (or pdf) by hand...

@belldandu
Copy link
Contributor

@typhoon71 That fetch of url error happens because the server returns a response other then 200.

@dteviot this ties into #13

We really also need to put in #14 an option for retrying if a server returns something other than 404 when it doesn't return 200.

@typhoon71
Copy link
Author

I don't know wh ythat error happens, and it's strange because I was able to fetch the whole thing before without issues. It seems it's still avail to me?

@dteviot
Copy link
Owner

dteviot commented Jun 30, 2016

@typhoon71 Belldandu is saying that the server is returning some response other than 200 (success), I'm going to guess you were getting a 50x series network error (unable to get file, usually due to some problem with the CDN.) Under that case, the generator just gives up. Obviously, better error reporting is required.

@typhoon71
Copy link
Author

But it should give success, if I just browse to the images I can open them... so the CDN should be working.
I mean, in this case I would expect a 200 -only-, nothing else.

@dteviot
Copy link
Owner

dteviot commented Jun 30, 2016

@typhoon71 Stupid questions,

  • is it only Firefox that has problems, or does the Crome version have same problem?
  • Does it work for older Firefox versions? If so, which ones?

@belldandu
Copy link
Contributor

belldandu commented Jun 30, 2016

@typhoon71 Another few stupid questions,

  • does this only happen on this specific page?
  • if not, what other pages does this happen on?

@dteviot
Copy link
Owner

dteviot commented Jul 1, 2016

Interesting, on Firefox, the images download and the epub is built, but the xhtml files are not correct.
The style information is visible in an epub viewer. Will investigate further, later.

@typhoon71
Copy link
Author

Not a stupid question at all, didn't think of checking that.
I manually installed the plugin in chrome (to be 100% sure it's the same as in firefox) and it packs the epub.
There are 2 buts: the plugin manager windows has some errors after loading it:

errors

and sigil sometime complains about malformed html on some novels.
https://baka-tsuki.org/project/index.php?title=This_title_is_too_long%21%3AVolume2 is affected, for example.

Since I started using this plugin I didn't update firefox, it's always been 47.0; I started having issues with the plugin 0.0.0.8, before it worked (I mean, it didn't just trow that error and stop).

To answer the last question, the problem with firefox happens on any page, it's not limited to the one I linked you.

@typhoon71
Copy link
Author

Small update, happens with Firefox 47.0.1 too (just updated).
I see minimum_firefox_version is set to 48... which is still beta... it would be sensible to set it to 47 instead.

@belldandu
Copy link
Contributor

belldandu commented Jul 1, 2016

The reason the minimum firefox version is 48 is because its using WebExtensions which is only supported by BETA/Aurora Firefox @typhoon71

@dteviot The reason he is getting these issues is more then likely because he is trying to use the extension on an unsupported version.

Since i have Aurora installed i will investigate this later and put whether or not this is reproducible in Aurora.

@typhoon71
Copy link
Author

I understand why you're using WebExtensions, but wouldn't it make sense to wait to intruduce them till Firefox 48 is released? Even keeping < Firefox 48 would be nice, after all there's the matter of what will happen when Mozilla will kill XUL & friends; some may decide to stay on older releases to wait and see what happens to the extensions... (a bloodbath I suppose).
This from a Firefox user standpoint; from a chrome user standpoint, it's irrelevant.

@belldandu
Copy link
Contributor

The reason we have not waited is for people to test it on the Aurora release so that we can scratch away any bugs before it becomes a stable version of firefox.

@belldandu
Copy link
Contributor

Also as for those manifest key errors thats because the firefox manifest and chrome manifest are one file so chrome doesn't know what to do with the keys. You can safely ignore those errors.

@typhoon71
Copy link
Author

OK, so I guess that I'll have to use chrome to make epubs, since the plugin now doesn't work on Firefox < 48...
I won't ask to not use WebExtensions, I just hope that Firefox 48 doesn't break anything...

@typhoon71
Copy link
Author

my bad, wrong button.

@typhoon71 typhoon71 reopened this Jul 1, 2016
@belldandu
Copy link
Contributor

belldandu commented Jul 1, 2016

Just Tested on https://baka-tsuki.org/project/index.php?title=CubexCursedxCurious:Volume1 seems to work fine. Although i do get your error message on https://baka-tsuki.org/project/index.php?title=CubexCursedxCurious But i think its obvious why.

@belldandu
Copy link
Contributor

see #37

@typhoon71
Copy link
Author

About the issue on firefox: I suppose it works in aurora, but I'll wait for ffox 48 to be released before testing.

About Sigil complaints, I get none on C3 volume 1. Maybe in some cases it happens, in some it doesn't.
Regarding "https://baka-tsuki.org/project/index.php?title=This_title_is_too_long%21%3AVolume2", the malformed html seems to be "0005_Afterword.xhtml", but I don't see anything strange opening the epub with calibre or even sumatra.

@dteviot
Copy link
Owner

dteviot commented Aug 21, 2016

As far as I can tell, all issues raised here are either fixed or documented as part of other issues. So closing.

@dteviot dteviot closed this as completed Aug 21, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants