Skip to main content


 
!iSurf Support

Today I noticed I cannot type in the reply box. I have to click comment on someone else's comment to post to an existing thread. Did something change on the server?

Yesterday I disabled the XMPP add-on, that was it. Otherwise, nothing's changed.

I didn't have any issue replying/commenting on your post here.

When I click in the box that says reply to Shelenn Ayres (original poster) the box goes back to unclicked state. I have to click Comment under your post to respond which then forces indent.

I would go through the usual routine of disabling add-ons, try another browser, etc...

Commenting fine here in the "reply to Shelenn Ayres (original poster)" comment box.

What browser? I am using the latest Chrome but it may have auto updated causing an issue.

Testing with Firefox works. Something changed in Chrome.

Checking my Chrome i get Version 73.0.3683.86 (Official Build) (64-bit)

Friendica works in FF though... but i also need to update FF with a fresh download... it will ahve to wait until after my dj event coming up

Testing with latest FF dev edition... works well and fast
This entry was edited (3 months ago)

Image/Photo" target="_blank">https://www.unicode.org/L2/L2018/18080-accessibility-emoji.pdfImage/Photo
This entry was edited (3 months ago)

Those are awesome :)

@Shelenn Ayres I am seeing this too on isurf conversations page.

I hadn't checked up on this, but looks like a fix was posted.

Please go ahead and try again - I just tested locally and it seems to be working better now.

@Adam Clark Still not working on Chrome.

@Shelenn Ayres this is from the "reply to shelenn Ayres" field. It works only if I click and HOLD and type a letter. The I can let go and finish. Let's see if it posts?

@Shelenn Ayres works in Firefox, but not Brave (chromium-based)

@Shelenn Ayres Chrome now, same thing I can "force" it to work (good to know) but it doesn't stay open on it's own. It acts like a door with an auto close mechanism. If you hold open and let a letter through, the rest can follow.

An issue was opened so the devs are aware and will get to it as they can :) We do have viable workarounds as you tested.

I wonder if you're running off a cached copy of the affected .js file? I've only tested under Chrome on Linux, which I did see the problem with previously, and I'm using Chrome as I write this, and have checked against numerous posts and it's working fine since I applied the little fix yesterday afternoon.

No the issue still persists with the version of Chrome noted above. I am a Win10 Pro user - not sure about the others.

@Shelenn Ayres Ok, I am posting on Brave (Chrome-based), I did a "Shift/Cmd R" which should empty the cache and the problem is indeed solved here. Thank you Adam!
This entry was edited (3 months ago)

Without doing anything in Chrome, it suddenly works (been out sick).

Magic! :-D

@Shelenn Ayres Cache probably updated. Seems to be fixed.