http://qs1969.pair.com?node_id=207248

Those of you who use the FullPage Chat may be interested in some patches that have been applied:

  1. The bottom frame has been removed to provide more real-estate for messages. (patch submitted by theorbtwo.)

  2. Links in the Chat Messages panel now open in new windows (Patch submitted by theorbtwo.)

  3. Links in the Other Users panel now open in new browser windows (patch submitted by theorbtwo.)

  4. The code has been modified to improve W3C validation, though it appears some work remains. (Based on a patch submitted by OeufMayo1).

  5. The top panel has been lengthened slightly to reduce clipping.

Please give this a spin and let me know if there are any problems. Also, feel free to buy the submitting monks a round next time they're in your neck of the woods.

--f

1 - Update: Fixed attribution for #4, after VSarkiss kindly asked me to check that. Major apologies to both monks.

Replies are listed 'Best First'.
Re: Tweaks Made to FullPage Chat
by BrowserUk (Patriarch) on Oct 23, 2002 at 02:27 UTC

    Much nicer. theorbtwo++ & OeufMayo++.

    One minor niggle. Is there any reason that the edit field couldn't be made to fill the header bar? This might help me (and a few others) to avoid some of those annoying typos because I can't see everything that I've typed.

    Then the button could have the text "Talk to" with the effect that the whole thing would read "Talk to Perl Monks" :^).


    Cor! Like yer ring! ... HALO dammit! ... 'Ave it yer way! Hal-lo, Mister la-de-da. ... Like yer ring!
Re: Tweaks Made to FullPage Chat
by mojotoad (Monsignor) on Oct 23, 2002 at 20:26 UTC
    I like the changes, however:

    • Links in the Chat Messages panel now open in new windows (Patch submitted by theorbtwo.)
    • Links in the Other Users panel now open in new browser windows (patch submitted by theorbtwo.)

    But links in the /msg frame do not -- they still open in the frame. Can we fix this one as well?

    Good work, guys. Thanks!
    Matt

    Update: It seems that the code has been patched with a base tag specifying a target of _new. This is good, but now the form for the submit button needs a target specified as _self.

      This appears to have been fixed... with as a side effect that form submission also opens in a new window! I'm sure it's the global target "_new" in the "base" tag that makes that happen. Adding a target attribute "_self" to the form tag, should do the trick.
Re: Tweaks Made to FullPage Chat
by mojobozo (Monk) on Oct 23, 2002 at 16:19 UTC
    I like the updates. ++ to you all! I also agree with BrowserUK, bigger text field, please. Other than that, it looks and works great!
    _____________________________________________________
    mojobozo
    word (wûrd)
    interj. Slang. Used to express approval or an affirmative response to
    something. Sometimes used with up. Source
Re: Tweaks Made to FullPage Chat
by the pusher robot (Monk) on Oct 23, 2002 at 22:20 UTC
    When I view it with Netscape 4.7 (not my choice, that's all that's available at work) at 1280x1024, the top frame is too small, so I'm only able to see the top of the text field. Looks good other than that.
•Re: Tweaks Made to FullPage Chat
by merlyn (Sage) on Oct 23, 2002 at 22:28 UTC
    It's still not working. It has never worked for me. It now says:
    Not Found The requested URL /'/index.pl was not found on this server.
    in the "chat" window after my first submission. I suspect you are sending out BAD html, which is being error-corrected by your so-called browser, but refused by a more correct browser. Please be sure your page is proper HTML.

    -- Randal L. Schwartz, Perl hacker
    Be sure to read my standard disclaimer if this is a reply.

      This is the refresh meta tag as it is now:
      <meta http-equiv="refresh" content="12; url='/index.pl?displaytype=ra +w&node_id=3200'" />
      According to several tutorials I found, one shouldn't put those single quotes around the URL, for example Webmonkey and indiana.edu.

      So this tag should really look like:

      <meta http-equiv="refresh" content="12; url=/index.pl?displaytype=raw +&node_id=3200" />
      At least merlyn's browser falls over the presence of that opening single quote.
        So this tag should really look like:
        <meta http-equiv="refresh" content="12; url=/index.pl?displaytype=raw +&node_id=3200" />
        No, it should really be:
        <meta http-equiv="refresh" content="12; url=/index.pl?displaytype=raw +&amp;node_id=3200" />
        You forgot the HTML escaping step. Just like most of Everything2 does, last time I looked. And it's all broken.

        -- Randal L. Schwartz, Perl hacker
        Be sure to read my standard disclaimer if this is a reply.

        Discussion of this issue went on for a while, so I'll just sum it up here:

        Nobody was able to find anything constituting anything like a W3C standard governing the content of content attributes of meta refresh tags. bart is correct in pointing out, (AFAIK) that no browser appears to fail if the single quotes around the URL "sub-attribute" are omitted, so if the darn things are going to be used and not proper HTTP headers, well, then it's best to omit the quotes (although I found examples containing quotes on a site owned by the same miscreants that appear to have invented this mess.

        W/ most browsers, the "sub-attribute" is only needed if the refresh tag is one of those cheesy redirects (my technical term of choice). Refreshing the same page needs only a time.

        For those of you who are interested, this was the closest thing I could find to a "reference" on the subject. Yes, not only did they invent <blink>, this, too is their fault =)

        If not P, what? Q maybe?
        "Sidney Morgenbesser"

      This has been fixed. Fullpage Chat should now work on pretty much all browsers.

      Makeshifts last the longest.

      For the record, although I've already mentioned this in the chatterbox, links has the same problem.

      Makeshifts last the longest.