RT 3.8.4 - adding comments with Google Chrome

RT Users
1

Hi all,

We’re using RT 3.8.4 on Ubuntu 10.10. I’ve noticed recently that the
textarea that is used to input comments on tickets is not displaying when
I’m using Google Chrome. I have 9.0.587.0 but the issue occurred on releases
prior to that. Nothing has changed for our setup except the updates to
Chrome, so I’m assuming that it’s related.

If I use IE or Firefox - no problem.

From the source produced by …/Ticket/Update.html, in firefox:

In Chrome: I suspect this behavior is programmed in. It used to work OK. Is there a workaround or a fix for this? Thanks, Gary
2

I’ve seen this with very recent versions of Chrome and RT’s RichText composer on a variety of versions of RT. I’m not yet sure what they changed, but we’re looking into it.On Mon, Nov 22, 2010 at 02:26:26PM +0000, Gary Holmes wrote:

Hi all,

We’re using RT 3.8.4 on Ubuntu 10.10. I’ve noticed recently that the
textarea that is used to input comments on tickets is not displaying when
I’m using Google Chrome. I have 9.0.587.0 but the issue occurred on releases
prior to that. Nothing has changed for our setup except the updates to
Chrome, so I’m assuming that it’s related.

If I use IE or Firefox - no problem.

From the source produced by …/Ticket/Update.html, in firefox:

In Chrome: I suspect this behavior is programmed in. It used to work OK. Is there a workaround or a fix for this? Thanks, Gary
3

it’s indeed a bug of fckeditor, I have filed a bug report,
see #6717 (fckeditor doesn't show up with chrome 9) – CKEditor

best wishes
sunnavyOn 10-11-22 14:26, Gary Holmes wrote:

Hi all,

We’re using RT 3.8.4 on Ubuntu 10.10. I’ve noticed recently that the
textarea that is used to input comments on tickets is not displaying when
I’m using Google Chrome. I have 9.0.587.0 but the issue occurred on releases
prior to that. Nothing has changed for our setup except the updates to
Chrome, so I’m assuming that it’s related.

If I use IE or Firefox - no problem.

From the source produced by …/Ticket/Update.html, in firefox:

In Chrome: I suspect this behavior is programmed in. It used to work OK. Is there a workaround or a fix for this? Thanks, Gary
4

actually, it’s chrome’s bug, which is fixed already, and I believe
the fix will be included in the next release of chrome.

see also Google Code Archive - Long-term storage for Google Code Project Hosting.

for users who want it now, I attached the workaround patch too.

best wishes
sunnavyOn 10-11-25 08:35, sunnavy wrote:

it’s indeed a bug of fckeditor, I have filed a bug report,
see #6717 (fckeditor doesn't show up with chrome 9) – CKEditor

best wishes
sunnavy

On 10-11-22 14:26, Gary Holmes wrote:

Hi all,

We’re using RT 3.8.4 on Ubuntu 10.10. I’ve noticed recently that the
textarea that is used to input comments on tickets is not displaying when
I’m using Google Chrome. I have 9.0.587.0 but the issue occurred on releases
prior to that. Nothing has changed for our setup except the updates to
Chrome, so I’m assuming that it’s related.

If I use IE or Firefox - no problem.

From the source produced by …/Ticket/Update.html, in firefox:

In Chrome: I suspect this behavior is programmed in. It used to work OK. Is there a workaround or a fix for this? Thanks, Gary

fckeditor.diff (1 KB)

5

I can confirm that it is indeed fixed with Chrome 9.0.597.0

GaryOn 29 November 2010 04:50, sunnavy sunnavy@bestpractical.com wrote:

actually, it’s chrome’s bug, which is fixed already, and I believe
the fix will be included in the next release of chrome.

see also Google Code Archive - Long-term storage for Google Code Project Hosting.

for users who want it now, I attached the workaround patch too.

best wishes
sunnavy

On 10-11-25 08:35, sunnavy wrote:

it’s indeed a bug of fckeditor, I have filed a bug report,
see #6717 (fckeditor doesn't show up with chrome 9) – CKEditor

best wishes
sunnavy

On 10-11-22 14:26, Gary Holmes wrote:

Hi all,

We’re using RT 3.8.4 on Ubuntu 10.10. I’ve noticed recently that the
textarea that is used to input comments on tickets is not displaying
when
I’m using Google Chrome. I have 9.0.587.0 but the issue occurred on
releases
prior to that. Nothing has changed for our setup except the updates to
Chrome, so I’m assuming that it’s related.

If I use IE or Firefox - no problem.

From the source produced by …/Ticket/Update.html, in firefox:

<textarea class="messagebox" cols="72" rows="15" name="UpdateContent"

id=

“UpdateContent”>

In Chrome:

I suspect this behavior is programmed in. It used to work OK. Is there a workaround or a fix for this? Thanks, Gary