15 comments

[ 167 ms ] story [ 200 ms ] thread
At least for now, you can get around the 100 char limit for titles in YCNews by first submitting with a shorter title and then editing it to have all the chars you want.
And dramatically decrease your chances of anyone actually clicking on it (except for me).
I am not advocating it :-)

I wanted to give the gist without the user having to click thru to find out. Those who want to actually use that JS library will click through, of course.

Plus, won't you agree with the "because I can" factor in wanting to try it? :-)

Yes.

Actually, (like most things), this makes me want to look for the opportunity. A new AI app - I can see it now...

Inputs: LongTitle and CharacterLimit

Output: MostEnticingUnderLimitTitle

In your case:

"Use JS Lib to Make MS IE Suk Less"

I actually did that the first time: "JS lib to make IE behave like a standards-compliant brwsr. Fixes HTML,CSS,PNG issues under IE5 & 6." (exactly 100 chars)

But when you can trick the system to let you have more than 100 chars, its kinda cool to do it.

Wow! I saw them fix it! Got "page cannot be displayed" for a second and then the title was shortened. Just a blip like deja vu glitch in the Matrix.
Nothing different happens when an item is in the middle of being edited, either by the submitter or the editors. The next request after the edit is saved just gets the new version.
This hole isn't there because I wasn't aware of it, but because I trust users here. Writing code to enforce rules is boring, so my general approach to abuse is to wait for it to happen before I expend time preventing it.
I have the same system, unfortunately people seem to do stupid things all the time.
I tried this library sometime around May of last year. I read through a wrox book called "CSS Instant Results" and many of the discussed CSS layouts required use of the IE7 script to work properly. I had some problems with the max/min width/height adjustments not holding when the browser was resized, and additionally there was some flicker when resizing. At the time, it appeared from the site and forum that there was not a lot of active development going on. Now it looks like there has been an update, and active development has resumed, so I would be interested to look into it again in the future.
Seems like this script does a top level document search for nodes to apply it's PNG fix. This can really hurt performance for sites that have complicated layouts. Sometimes it's best just manually code your own png fix solutions (fix exactly the image and div nodes you need for each page, rather than conducting a document.getElementsByTagName.. sweep)
Doesn't seem to fix the shimming problem :/