various ^H hacks (30, permasaged)

1 Name: Anonymous : 2009-04-14 15:36 ID:X2jEAV7V [Del]

Bug in wakautils.pl/do_spans:

You can use ^H to kill parts of previously parsed HTML tags, e.g. if you may cut <strong> to non-closed <s making it strike the whole page, or cut <!--$#hidden--> to <!-- and --> in some other thread to hide portions of page. Have somebody ever fixed this without disabling ^H completely?

2 Post deleted by user.

3 Name: Anonymous : 2009-04-14 15:39 ID:X2jEAV7V [Del]

>>2
See, it works even here. BTW, Firefox dies with "not well-formed XML" unless you have USE_XHTML = 0.

4 Name: Anonymous : 2009-04-14 16:26 ID:Heaven [Del]

^U^U^U^U

5 Name: Anonymous : 2009-04-14 16:53 ID:SIiqJ65g [Del]

<ttt>testo </ttt>

6 Post deleted by moderator.

7 Post deleted by user.

8 Name: Anonymous : 2009-04-14 19:19 ID:Heaven [Del]

Well, while we're at it, theres a rather serious bug with the html tag parser -- or rather, it's completely functional, apart from the fact that it's not an html parser at all. If you write <em/> it won't convert it to <em></em> like it ought, and browsers don't parse the resulting page "correctly". I've tried it with firefox, opera, safari, and msie, and they all end up making the whole rest of the page italic. Same goes with <strong> and so on.

(And there really should be <code> or <tt> or something in the allowed html tags list.)

9 Name: Anonymous : 2009-04-14 19:20 ID:Heaven [Del]

<strong/>
Example of previous post. This should not be bold, but browsers get completely confused by the self-closing tag.

10 Name: Anonymous : 2009-04-14 19:21 ID:Heaven [Del]

Errr...

Probably want the right markup format.

11 Name: Anonymous : 2009-04-16 01:54 ID:Heaven [Del]

you know there is a thread for testing things...
http://wakaba.c3.cx/sup/kareha.pl/1099697376/l50

12 Post deleted by user.

13 Name: !WAHa.06x36 : 2009-04-16 11:09 ID:Heaven [Del]

>>8

Well, it's not a HTML parser, it's an XHTML parser. I guess it's probably a bad idea to have it enabled if pages aren't sent as XHTML... Not sure what to do about that.

I guess the bug should be fixed, though.

14 Name: !WAHa.06x36 : 2009-04-16 11:39 ID:/Tpx7oh3 [Del]

It's sure been a while since I messed with this code base, so I might have gotten something wrong, but here we go:

http://wakaba.c3.cx/releases/kareha_3.1.4.zip
http://wakaba.c3.cx/releases/wakaba_3.0.8.zip

There are some older bugfixes and such rolled in too. Somebody try it out and tell me if it works as it should.

15 Name: ‮‮ : 2009-04-16 12:57 ID:U0pjXIf7 [Del]

what about unicode char U+202E RIGHT-TO-LEFT OVERRIDE in thread title? In this post in name field U+202E char

16 Name: Anonymous : 2009-04-16 16:46 ID:IZn6htHI [Del]

>>14
Thanks!

>>15
Not a bug IMO: board behaves like every other thing you can feed your 202e to, thus no need to fix it.

17 Name: iSage!ISage.aan6 : 2009-04-17 01:45 ID:VMAfDL2p [Del]

>>14
looked into the code

diff -EBbr --normal ./wakaba.pl ../wakaba_new/wakaba.pl
19c19
< BEGIN { require "futaba_style.pl"; } # edit this line to change the board style
---
> BEGIN { require "oekaki_style.pl"; } # edit this line to change the board style

that's wrong.

also,
491a492

>               included_fields=>["field1","field2","field3","field4"],

that should be "name","email","subject","comment"

18 Name: !WAHa.06x36 : 2009-04-17 11:04 ID:/Tpx7oh3 [Del]

>>17

Fixed the first, the second is not a mistake.

Name: Link:
Leave these fields empty (spam trap):
More options...
Verification: