I will look at getting it into 3.5 in the next couple of hours.
For future search users: If you have "Require well formed HTML" checked in your wolips preferences it will be parsed "strictly" and any attempt to reformat a component with invalid markup *WILL* cause it to get clobbered. If that option isn't checked, then you should be good.
On 07/06/2010, at 9:22 AM, Kieran Kelleher wrote:
> Hey, thanks Quinton.
>
> On Jun 6, 2010, at 5:28 PM, Q wrote:
>
>> I committed a fix for this to the 3.6 nightly branch but haven't seen an email for it from SVN. Will backport the change to 3.5 once I confirm it's working correctly.
>>
>> Sent from my iPhone
>>
>> On 04/06/2010, at 9:47 AM, Mike Schrag <mschra..obox.com> wrote:
>>
>>>> The formatter doesn't work very well with invalid markup because it is based on an XML parser. If you fix the <br> tag it should format correctly.
>>> i went through a bunch of pains back in the day to make it parse that kind of crappy syntax, though ... it SHOULD actually work. i'm not really sure what happened here. I presume that ended up as an illegitimate child of the <br> tag, and maybe formatting tossed it because br is treated in a special way in a couple places. definitely a bug. stuff disappearing on format is uncool.
>>>
>>> ms
>
-- Seeya...QQuinton Dolan - qdola..mail.com Gold Coast, QLD, Australia (GMT+10)
This archive was generated by hypermail 2.0.0 : Mon Jun 07 2010 - 00:12:25 UTC