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

Possible issue when writing long text in Jetpack Comments ? (contentWindow . size) #3453

Open
MisterWP opened this issue Feb 25, 2016 · 3 comments
Labels
[Feature] Comments [Type] Bug When a feature is broken and / or not performing as intended

Comments

@MisterWP
Copy link

Hi!

What I expected

Write a long comment in a website "http" using Jetpack Comments in Google Chrome.

What happened instead

Finally, the textarea truncate the text and the submit button comes hidden.

Steps to reproduce the issue

I obviously check everything about my website (css,...), not max-width / overflow:hidden / ... defined, but, curiously, without any update in my website, the problem happened overnight :-o so, I think, maybe an issue good to report you.

During my test to solve the issue, I discovered that maybe, the self-hosted website cannot get the "contentWindow".size inside the Jetpack Comments "iframe". Maybe a conflict of mixed content HTTP/HTTPS ? I don't know.
Here a screenshot :
https://pbs.twimg.com/media/CbvnakKUMAAbMl4.png

I hope do not make you lose your precious time.

Good day & Kisses, all the team ! 👍

@kraftbj kraftbj added [Type] Bug When a feature is broken and / or not performing as intended [Feature] Comments labels Feb 25, 2016
@kraftbj kraftbj added this to the 4.0 milestone Feb 25, 2016
@jeherve
Copy link
Member

jeherve commented Feb 25, 2016

Thanks for the detailed report. We'll run some more tests.

Related: #2841

@jeherve jeherve modified the milestones: 4.1, 4.3 Jun 17, 2016
@richardmuscat richardmuscat modified the milestones: 4.3, 4.4 Jul 7, 2016
@jeherve jeherve modified the milestone: 4.4 Jul 8, 2016
@samhotchkiss samhotchkiss modified the milestones: 4.4, Not Currently Planned Nov 9, 2016
@mpeshev
Copy link
Contributor

mpeshev commented Jun 23, 2017

I can definitely reproduce the same problem on my blog. Recently, I've received several different reports for the same problem as well. Absolutely identical to what MisterWP has reported in the original issue.

@stale
Copy link

stale bot commented Jul 3, 2018

This issue has been marked as stale. This happened because:

  • It has been inactive in the past 6 months.
  • It hasn’t been labeled `[Pri] Blocker`, `[Pri] High`.

No further action is needed. But it's worth checking if this ticket has clear reproduction steps and it is still reproducible. Feel free to close this issue if you think it's not valid anymore — if you do, please add a brief explanation.

@stale stale bot added the [Status] Stale label Jul 3, 2018
@kraftbj kraftbj removed this from the Not Currently Planned milestone Jan 26, 2021
@stale stale bot removed the [Status] Stale label Jan 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] Comments [Type] Bug When a feature is broken and / or not performing as intended
Projects
None yet
Development

No branches or pull requests

6 participants