• Rhialto (unregistered) in reply to Whoevar
    Whoevar:
    Whoevar:
    Why Two Kay:
    At least the page looks okay, aesthetically speaking.
    Not using Opera 9.64 ;-)
    It looks even worse in Firefox if you use NoScript. Even the submit buttons (or what I suppose them to be) do nothing.
  • IMSoP (unregistered) in reply to Eric
    Eric:
    When the browser performs a post, ASP.Net will check the values from the ViewState against the values being posted for each of those elements and raise events appropriate to what has happened to the state of the elements since the last post, such as OnSelectedIndexChanged for a dropdown.

    Maybe it's just because I've not seen the way ASP.Net is coded, but I don't get why you'd ever need that - surely, when a form is posted, only one event needs to fire: the form submission, with the current state of all form controls.

    The fact that a drop-down has changed is irrelevant - the time to react to that is when the user makes the change, i.e. with a JavaScript onchange event. By the time the form is submitted, that event is in the past, so what's the point?

  • Jon (unregistered) in reply to IMSoP
    IMSoP:
    Eric:
    When the browser performs a post, ASP.Net will check the values from the ViewState against the values being posted for each of those elements and raise events appropriate to what has happened to the state of the elements since the last post, such as OnSelectedIndexChanged for a dropdown.

    Maybe it's just because I've not seen the way ASP.Net is coded, but I don't get why you'd ever need that - surely, when a form is posted, only one event needs to fire: the form submission, with the current state of all form controls.

    The fact that a drop-down has changed is irrelevant - the time to react to that is when the user makes the change, i.e. with a JavaScript onchange event. By the time the form is submitted, that event is in the past, so what's the point?

    ASP.NET has this "AutoPostBack" 'feature' where it will cause a postback (i.e. submit the form!) whenever the drop-down changes (if you want it to).

  • Laere (unregistered) in reply to IMSoP

    For example, if you have a paged datagrid on your webpage, it will keep the parametrization of the grid (sorting, filtering, selected page etc...). You don't have to bother with it, the datagrid options will be automatically repopulated.

    It's useful when used wisely... But Microsoft used it intensively in their webcontrols. I mean, paging or ordering is ok. But really, should they add texts and styles to the viewstate? It was (I think) a good idea. Now it's just awful.

  • Jorge (unregistered) in reply to AndrewB

    I always have like this one better:

    28 2E 29 20 28 2E 29 20 29 20 2E 20 28 20 28 20 20 59 20 20 29

  • idan (unregistered) in reply to Scott
    Scott:
    To be fair, they've recently diverted most of their resources previously allocated to web development towards killing Palestinians.

    LOL! You just made my day!

  • JuanCarlosII (unregistered) in reply to Jon
    Jon:
    IMSoP:
    Eric:
    When the browser performs a post, ASP.Net will check the values from the ViewState against the values being posted for each of those elements and raise events appropriate to what has happened to the state of the elements since the last post, such as OnSelectedIndexChanged for a dropdown.

    Maybe it's just because I've not seen the way ASP.Net is coded, but I don't get why you'd ever need that - surely, when a form is posted, only one event needs to fire: the form submission, with the current state of all form controls.

    The fact that a drop-down has changed is irrelevant - the time to react to that is when the user makes the change, i.e. with a JavaScript onchange event. By the time the form is submitted, that event is in the past, so what's the point?

    ASP.NET has this "AutoPostBack" 'feature' where it will cause a postback (i.e. submit the form!) whenever the drop-down changes (if you want it to).

    ... and it's one of the worst ideas ever if you want anyone to be able to navigate through your form using keyboard controls.

    Finding your country in a select box of 200 countries is hard enough, now suppose that the page reloads each time you try to scroll through the options.

  • (cs) in reply to John
    John:
    I use VS to help with the forms, check the generated source and remove any of the crud.

    It's all XHTML1.1 compliant. It's one of my requirements (all pages have to have a W3 strict XHTML link) and one of the major reasons I had put it off.

    It validates on w3.org, VS applies styling in stylesheets rather than inline (finally, though not intelligently). Pages have to render properly in IE6+, Chrome, Firefox, Safari & Opera.

    So you're sending that as text/xml because of IE6 are you? After all, that's a (crappy) fallback for what the content type should be for XHTML1.1; application/xhtml+xml

    Alternatively, you're actually writing valid (and compliant) XHTML1.0 Strict but just telling the validator you're writing XHTML1.1.

  • Hallvord R. M. Steen (unregistered) in reply to Whiskey Tango Foxtrot? Over.

    Hi, there are indeed some angle brackets in the article text that were meant to appear as entities.

    Starting from "Hence, < is sometimes escaped as < to create" - the second angle bracket and most of the others in the following text should be entities. If you read it closely you can figure out which ones..

    I'm flattered to see my submission on the Daily WTF, of course. Thanks, Alex :)

    Hallvord R. M. Steen http://my.opera.com/hallvors/blog/

  • Anonym (unregistered) in reply to jordanwb
    jordanwb:
    A related fail: ... Ubuntu ...
  • John (unregistered) in reply to MrBester
    MrBester:
    John:
    I use VS to help with the forms, check the generated source and remove any of the crud.

    It's all XHTML1.1 compliant. It's one of my requirements (all pages have to have a W3 strict XHTML link) and one of the major reasons I had put it off.

    It validates on w3.org, VS applies styling in stylesheets rather than inline (finally, though not intelligently). Pages have to render properly in IE6+, Chrome, Firefox, Safari & Opera.

    So you're sending that as text/xml because of IE6 are you? After all, that's a (crappy) fallback for what the content type should be for XHTML1.1; application/xhtml+xml

    Alternatively, you're actually writing valid (and compliant) XHTML1.0 Strict but just telling the validator you're writing XHTML1.1.

    Yup, I adhere to standards as strictly as I can. However we don't live in a utopia yet and I can't afford not to serve pages to a large proportion of web users. I'm all for standards but good god, some people appear to have a chip on their shoulders the size of Gibraltar when you mention Microsoft. In the words of Denis Leary "Life sucks... wear a fucking helmet"

  • ModernProgramming (unregistered) in reply to Jorge
    Jorge:
    I always have like this one better:

    28 2E 29 20 28 2E 29 20 29 20 2E 20 28 20 28 20 20 59 20 20 29

    Shaved Pussy?

  • erikmack (unregistered)

    The array of legal URL chars is not that abnormal. The dev probably has experience writing lexers/parsers, where it's common to use an array of the first 128 ASCII characters to group characters into classes.

    DNS, though, is supposed to accept Unicode characters now.

    As far as XSLT, yeah... I've read many times that "XSLT is Turing-complete", but some people take that as a challenge. I don't think there are many XSLT debuggers out there, so I'm sorry for the next dev that has to maintain it.

  • Schmirkeley Wirkeley (unregistered) in reply to John
    John:
    synp:
    John:
    synp:
    NightDweller:
    synp:
    According to the site, it was built by netwise. I guess it's these guys:

    http://www.netwise.co.il/Templates/HomepageEng.aspx

    To get a good sense of how good it is, you should take a look at their Hebrew homepage. (and no, its not your browser, that's the actual page..i tried with Firefox 3.0.7 and IE7)

    Kinda ugly, but what's wrong with it?

    Works OK in Safari.

    Very definately ugly. Who in their right mind would align-right all the text?

    You didn't even look. It's all centered.

    Very definitely right aligned: [image]

    Not to be facetious, but it's right-aligned because Hebrew reads from Right-To-Left. It's as idiotic as any RTL native complaining that OMFG English speakers are left-aligning everything.

    Way

    No Way.

    Way.

  • synp (unregistered) in reply to John
    John:
    synp:
    John:
    synp:
    NightDweller:
    synp:
    According to the site, it was built by netwise. I guess it's these guys:

    http://www.netwise.co.il/Templates/HomepageEng.aspx

    To get a good sense of how good it is, you should take a look at their Hebrew homepage. (and no, its not your browser, that's the actual page..i tried with Firefox 3.0.7 and IE7)

    Kinda ugly, but what's wrong with it?

    Works OK in Safari.

    Very definately ugly. Who in their right mind would align-right all the text?

    You didn't even look. It's all centered.

    Very definitely right aligned: http://www.tipstrade.net/images/israel_rail.jpg

    Not on the homepage link that NightDweller linked...

  • synp (unregistered) in reply to Pim
    Pim:
    If the intent was to have the same info on the English language page as on the Hebrew one, I think they failed. That said, it does look the same in IE7 and SeaMonkey, so I'm not complaining.

    That is not always the intent. The site has Hebrew, Arabic, Russian and English. The Hebrew and Arabic should be roughly equivalent, as they are aimed at long-time Israelis. Russian is aimed at recent immigrants. English is aimed at tourists.

    It's possible that there are intentional differences.

  • Ron (unregistered)

    generally, Israel railways are consistently known for hiring based on whether you have some relative working for them rather than how skilled you are.

  • IMSoP (unregistered) in reply to erikmack
    erikmack:
    DNS, though, is supposed to accept Unicode characters now.

    Are you sure about that? My understanding was that it was up to applications to encode hostnames as "punycode" (and add the magic string "xn--"), so that the encoded version of the hostname still contains only those characters guaranteed to be safe on legacy infrastructure.

  • (cs) in reply to synp
    synp:
    John:
    synp:
    John:
    synp:
    NightDweller:
    synp:
    According to the site, it was built by netwise. I guess it's these guys:

    http://www.netwise.co.il/Templates/HomepageEng.aspx

    To get a good sense of how good it is, you should take a look at their Hebrew homepage. (and no, its not your browser, that's the actual page..i tried with Firefox 3.0.7 and IE7)

    Kinda ugly, but what's wrong with it?

    Works OK in Safari.

    Very definately ugly. Who in their right mind would align-right all the text?

    You didn't even look. It's all centered.

    Very definitely right aligned: http://www.tipstrade.net/images/israel_rail.jpg

    Not on the homepage link that NightDweller linked...

    True...I actually linked to the page that appears if you click on "עברית" (Hebrew) on their English page. In my defense, it does say "...Homepage.aspx" in the url to the Hebrew page...and also that apparently the link to the "Hebrew" version of the homepage and the actual Hebrew homepage do not point to the same location. I guess no one in this website design company ever clicked the "עברית" link in their English homepage.

  • JBB (unregistered)

    i don't know a thing about XSLT but isn't it acronym for Xml Stress Long Test ??

  • http://www.anselmoalves.com (unregistered)

    This is indeed the Boolean wall design pattern! :D

    var LegalUrlChars=new Array ( false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, true, true, false, false, true, false, false, true,
    true, true, false, true, true, true, true, true, true, true, true, true, true, true, true, true,
    true, true, false, true, false, true, false, false, true, true, true, true, true, true, true, true,
    true, true, true, true, true, true, true, true, true, true, true, true, true, true, true, true,
    true, true, true, true, false, true, true, true, true, true, true, true, true, true, true, true,
    true, true, true, true, true, true, true, true, true, true, true, true, true, true, true, true,
    true, true, true, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false, false );

  • lakera (unregistered)

    i dont know what this website is abouttt

Leave a comment on “Where the Wild Web Things Are”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article