Post page cut off on publish

y6nH commented

2019-03-29 17:52:51 +00:00

(Migrated from github.com)

This is a weird one.

I have been writing this post on fediverse.blog.

When I saved the draft or published it in its earlier form, the page got cut off part-way through. Not just the post content, the HTML file just ended half way through a word, without any closing tags. This was repeatable and consistent behaviour, in Firefox and Chrome. The full text was still there in the edit view.

The post would publish normally if I removed the banner image, or changed the title. If I edit this post and change the title to the original "Alpha, Beta, Gamma: Trying out Wendy Carlos's tunings", it happens again.

I have reproduced the issue in a draft post with a similar title, a different image and lorem ipsum content.

Plume version: 0.2.0
Operating system: Windows 10 and Linux Mint
Web Browser: Firefox 67 and Chrome 73

This is a weird one. I have been writing [this post on fediverse.blog]( https://fediverse.blog/~/YourSixNewHeads/alpha-beta-gamma-trying-out-wendy-carlos's-tunings). When I saved the draft or published it in its earlier form, the page got cut off part-way through. Not just the post content, the HTML file just ended half way through a word, without any closing tags. This was repeatable and consistent behaviour, in Firefox and Chrome. The full text was still there in the edit view. The post would publish normally if I removed the banner image, or changed the title. If I edit this post and change the title to the original "Alpha, Beta, Gamma: Trying out Wendy Carlos's tunings", it happens again. I have reproduced the issue in a draft post with a similar title, a different image and *lorem ipsum* content. - **Plume version:** 0.2.0 - **Operating system:** Windows 10 and Linux Mint - **Web Browser:** Firefox 67 and Chrome 73

y6nH commented

2019-04-29 12:07:03 +00:00

(Migrated from github.com)

Adding to this, I returned to the post today. Fediverse.blog has been updated to 0.3.0, and the published version (which was OK when I left it) got cut off again in the process.

trinity-1686a commented

2019-04-29 12:19:01 +00:00

Owner

I don't have the issue on the article you mentioned, but I do have it on another one. Maybe it only happen for article wrote by self?

I don't have the issue on the article you mentioned, but I do have it on [another one](https://fediverse.blog/~/PlumeDev/new-plume-alpha). Maybe it only happen for article wrote by self?

👍 1

y6nH commented

2019-04-29 15:14:50 +00:00

(Migrated from github.com)

I fixed my article by removing the header image, so it's back to full length. I still have a draft of a broken article, if anyone needs it.

trinity-1686a commented

2019-08-27 12:37:44 +00:00

Owner

I no longer have this issue on the article I linked, do you still have it?

y6nH commented

2019-09-02 13:18:40 +00:00

(Migrated from github.com)

No, it looks as if this is fixed. Fediverse.blog still says it's 0.3.0, so I don't know what changed.

serra-allgood commented

2019-11-14 09:51:54 +00:00

(Migrated from github.com)

Adding to this: With 0.3.0 and viewing in Firefox Developer Edition on macOS Catalina, if my published article has a cover image, it gets cut off towards the bottom; it displays fine in Chrome, however.

igalic commented

2019-11-14 10:17:20 +00:00

(Migrated from github.com)

perhaps this is a bug in Firefox that we should submit to https://github.com/webcompat/web-bugs/ ?

serra-allgood commented

2019-11-14 10:18:42 +00:00

(Migrated from github.com)

I agree that's a good idea, and I think it's worth tracking down what part of the Plume source interacts with Firefox this way before doing so

👍 1

y6nH commented

2019-11-14 18:04:57 +00:00

(Migrated from github.com)

I doubt this is a Firefox bug. For one thing, I saw it in Chrome too, and for another, the actual server response is truncated, not just the display of it in the browser. I know that doesn't 100% rule out a browser bug, but I'm not able to reproduce it any more.

serra-allgood commented

2019-11-14 18:59:10 +00:00

(Migrated from github.com)

I am able to consistently reproduce at https://write.allgood.mx/~/ItsAllgoodSerra/practical-cryptography-for-real-people by adding one of the two media images I have uploaded to my instance as an illustration. Adding an illustration causes a caught off in Firefox Developer Edition but not Chrome, both on macOS Catalina.

Serra C. Allgood
Software Engineer

any historical pronoun set accepted, xi/xer/xem preferred

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Thursday, November 14, 2019 10:05 AM, Hugh notifications@github.com wrote:

I doubt this is a Firefox bug. For one thing, I saw it in Chrome too, and for another, the actual server response is truncated, not just the display of it in the browser. I know that doesn't 100% rule out a browser bug, but I'm not able to reproduce it any more.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

I am able to consistently reproduce at https://write.allgood.mx/~/ItsAllgoodSerra/practical-cryptography-for-real-people by adding one of the two media images I have uploaded to my instance as an illustration. Adding an illustration causes a caught off in Firefox Developer Edition but not Chrome, both on macOS Catalina. --- Serra C. Allgood Software Engineer any historical pronoun set accepted, [xi/xer/xem](https://allgood.link/pronoun_preferences) preferred Sent with [ProtonMail](https://protonmail.com) Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Thursday, November 14, 2019 10:05 AM, Hugh <notifications@github.com> wrote: > I doubt this is a Firefox bug. For one thing, I saw it in Chrome too, and for another, the actual server response is truncated, not just the display of it in the browser. I know that doesn't 100% rule out a browser bug, but I'm not able to reproduce it any more. > > — > You are receiving this because you commented. > Reply to this email directly, [view it on GitHub](https://github.com/Plume-org/Plume/issues/507?email_source=notifications&email_token=AAR2K4P42BPIXM34YOU2MLLQTWHMZA5CNFSM4HCLXB62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEECX2II#issuecomment-554007841), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AAR2K4L4KQI2XKZLMFX6V73QTWHMZANCNFSM4HCLXB6Q).

trinity-1686a commented

2019-11-16 11:12:32 +00:00

Owner

I'm pretty sure this come from rocket_csrf (which we manage), but I've not been able to reproduce reliably to see what is wrong with it.
@serra-allgood the link you provide seems to require some authentication against Yunohost 😕

I'm pretty sure this come from [rocket_csrf](https://github.com/Plume-org/rocket_csrf) (which we manage), but I've not been able to reproduce reliably to see what is wrong with it. @serra-allgood the link you provide seems to require some authentication against Yunohost :confused:

serra-allgood commented

2019-11-16 11:19:39 +00:00

(Migrated from github.com)

Ah, sorry, I killed my plume instance not thinking about this thread :(

Serra C. Allgood
Software Engineer

any historical pronoun set accepted, xi/xer/xem preferred

Sent from ProtonMail mobile

-------- Original Message --------
On Nov 16, 2019, 03:12, fdb-hiroshima wrote:

I'm pretty sure this come from rocket_csrf (which we manage), but I've not been able to reproduce reliably to see what is wrong with it.
@serra-allgood the link you provide seems to require some authentication against Yunohost 😕

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Ah, sorry, I killed my plume instance not thinking about this thread :( --- Serra C. Allgood Software Engineer any historical pronoun set accepted, [xi/xer/xem](https://allgood.link/pronoun_preferences) preferred Sent from ProtonMail mobile -------- Original Message -------- On Nov 16, 2019, 03:12, fdb-hiroshima wrote: > I'm pretty sure this come from [rocket_csrf](https://github.com/Plume-org/rocket_csrf) (which we manage), but I've not been able to reproduce reliably to see what is wrong with it. > [@serra-allgood](https://github.com/serra-allgood) the link you provide seems to require some authentication against Yunohost 😕 > > — > You are receiving this because you were mentioned. > Reply to this email directly, [view it on GitHub](https://github.com/Plume-org/Plume/issues/507?email_source=notifications&email_token=AAR2K4MXEWLWXOAUDNC4NWLQT7ISHA5CNFSM4HCLXB62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEHPDJA#issuecomment-554627492), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AAR2K4LP4KBXQ6QAGLVFYTLQT7ISHANCNFSM4HCLXB6Q).

y6nH commented

2019-11-16 23:58:45 +00:00

(Migrated from github.com)

The post text is still available from Google cache, if anybody wants to search for clues. I noticed that both Serra's and my articles have a : in the title, though that isn't helping me reproduce it.

The post text is still available from [Google cache](http://webcache.googleusercontent.com/search?q=cache:https%3A%2F%2Fwrite.allgood.mx%2F~%2FItsAllgoodSerra%2Fpractical-cryptography-for-real-people), if anybody wants to search for clues. I noticed that both Serra's and my articles have a `:` in the title, though that isn't helping me reproduce it.

Rows
Columns

Post page cut off on publish #507