4 ms·
No idea what you mean, sorry. I'm just using Github's automatically generated web pages, so if there's a problem there it's probably a Github issue.
by captaincrowbar 11y ago
No idea what you mean, sorry. I'm just using Github's automatically generated web pages, so if there's a problem there it's probably a Github issue.
- geekone 11y agoProbably referring to the Documentation link you provide on the GitHub page, and it breaks back button for me too.
- funkaster 11y agoI think it's the htmlpreview: the back throws you into a redirection to the current page.
- captaincrowbar 11y agoI just tried that on several browsers; Safari and Chrome are fine, it seems to be only Firefox that has a problem with that. I have no idea whether that's a bug in Firefox or Github, and either way there's nothing I can do about it, sorry.
- funkaster 11y agoyes, you can: publish your docs as real web pages and not a link to the htmlpreview of a file inside your repo. That should fix the problem.
- dpark 11y agoI guess he should have said that there's nothing reasonable he can do about it. Creating an entirely separate set of HTML pages would require a new publishing flow, add a new step every time docs update, and generally encourage the docs to fall out of sync with the repo. He could do all of this, or he could do the sensible thing and leave the docs exactly like they are.
- lomnakkus 11y agoHmm... weird. I guess this should either be reported to the GitHub people and/or the Firefox people?