julieth756 / share-extras

Automatically exported from code.google.com/p/share-extras
0 stars 0 forks source link

Yammer-Dashlet: Message Encoding: Cannot handle messages with more than one space #46

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Click "New Update"
2. Enter a message with multiple words, separated by spaces.
3. Click "OK"
4. PopupManager will display: "Could not post message"

What is the expected output? What do you see instead?
  Expected output is a new status message update.
  PopupManager will display: "Could not post message" instead.

What version of the add-on are you using? Please provide version of the
downloaded package, or Subversion revision number.
  Yammer Dashlet and Share OAuth revision number: 676

What version of Alfresco are you using? On what application server?
  Alfresco 4.0a build 09/26/2011 on tomcat6

What web browser are you using? Please supply browser name and version.
  Chrome and IE8

Please provide any additional information below.
  found the bug in the oauth.js line:551
  replace(/%20/g, spaceChar) instead of replace("%20", spaceChar, "g")

Cheers, Jens
Greetings from Flo and Jan

Original issue reported on code.google.com by jens.plo...@gmail.com on 27 Sep 2011 at 11:21

Attachments:

GoogleCodeExporter commented 9 years ago
Hi, thanks for this report. Can you confirm the fix works for both Chrome and 
IE? The bug is interesting. According to the MDN docs, the flags should be 
specified on the regexp object and this works for Firefox, but obviously Chrome 
and IE use the non-standard third parameter for this.

Original comment by will.abson on 7 Nov 2011 at 2:25

GoogleCodeExporter commented 9 years ago
Yes it works for both, Chrome and IE.

Original comment by jens.plo...@gmail.com on 8 Nov 2011 at 9:46

GoogleCodeExporter commented 9 years ago
This issue was closed by revision r771.

Original comment by will.abson on 8 Nov 2011 at 8:07

GoogleCodeExporter commented 9 years ago
Fixed in SVN r771. I will create a file release once I have looked at a couple 
of other small items.

Original comment by will.abson on 8 Nov 2011 at 8:08