Closed (fixed)
Project:
Privatemsg
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
15 Jul 2010 at 22:55 UTC
Updated:
24 Aug 2010 at 20:00 UTC
Jump to comment: Most recent file
Comments
Comment #2
andypostTrying it for D7
Comment #3
andypostNow for d6
Comment #4
berdirThat span is there for a reason. You need to ask Michelle about how it works exactly, but we can't just remove it, that is going to break stuff.
Comment #5
michelleJust stumbled on this and, honestly, I'm not sure. Obviously it's not a simple typo so there was a reason when it was put in but I can't see a reason for it now. I'm guessing it had to do with the image handling because that's handled elsewhere with spans but, in this case the image handling is on the main class itself. I'm working on the AP integration with both versions of AF right now and will throw looking into this into the mix.
Michelle
Comment #6
andypost@Michelle I think jQuery should add this span while processing with http://api.jquery.com/append/ or similar to leave code valid.
Anyway thanx for review
Comment #7
berdirAsked Michelle and she just removed the same from another module and said that it is not required anymore. Applied the patches to all branches, thanks!