What to use intead of taget_new in XHTML/Strict

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • chris Jangelov

    What to use intead of taget_new in XHTML/Strict

    It seems that opening a link in a new window isn't considered to be good
    practise in xhtml 1.1. The w3c validation service does not accept it and I
    have to downgrade those pages to xhtml/transitional.

    Does anyone know what the proper solution would be to open a link in a new
    window if I want all my pages to comply with the xhtml/strict level?

    I can see the thought behind, I think, but I would argue that there are
    legitimate reasons for giving full control to the site I am linking to,
    while my (unexperienced) visitor still doesn't loose track of my site.

    I've searched the net for an answer/diskussion about this but haven't found
    anything. I would really appreciate some input.

    /chris
  • Chris Morris

    #2
    Re: What to use intead of taget_new in XHTML/Strict

    chris.jangelov@ hemsidan.info (chris Jangelov) writes:[color=blue]
    > It seems that opening a link in a new window isn't considered to be good
    > practise in xhtml 1.1. The w3c validation service does not accept it and I
    > have to downgrade those pages to xhtml/transitional.[/color]

    XHTML 1.1? Do you not have a significant number of Internet Explorer
    users (it doesn't work in IE6 or below). Unless you have a very good
    reason for using XHTML, stick to HTML 4.01.
    [color=blue]
    > Does anyone know what the proper solution would be to open a link in a new
    > window if I want all my pages to comply with the xhtml/strict level?[/color]

    You can't have both - you can either open in a new window, or use strict.
    [color=blue]
    > I can see the thought behind, I think, but I would argue that there are
    > legitimate reasons for giving full control to the site I am linking to,
    > while my (unexperienced) visitor still doesn't loose track of my site.[/color]

    There are, occasionally, good reasons to open a new window for a
    user. This, however, is almost never one of them. Your inexperienced
    visitor is far more likely to find their way back (should they want
    to!) if you don't break their back button by opening a new window.
    [color=blue]
    > I've searched the net for an answer/diskussion about this but haven't found
    > anything. I would really appreciate some input.[/color]

    Search Google Groups on this group. Many threads about this.

    --
    Chris

    Comment

    • Matthias Gutfeldt

      #3
      Re: What to use intead of taget_new in XHTML/Strict

      chris Jangelov wrote:[color=blue]
      > It seems that opening a link in a new window isn't considered to be good
      > practise in xhtml 1.1. The w3c validation service does not accept it and I
      > have to downgrade those pages to xhtml/transitional.
      >
      > Does anyone know what the proper solution would be to open a link in a new
      > window if I want all my pages to comply with the xhtml/strict level?[/color]

      If, as you say, it is bad practice in xhtml 1.1, then you probably
      shouldn't do it in xhtml 1.1.

      [color=blue]
      > I can see the thought behind, I think, but I would argue that there are
      > legitimate reasons for giving full control to the site I am linking to,
      > while my (unexperienced) visitor still doesn't loose track of my site.[/color]

      In that case use a Doctype that provides the feature you think you need.


      Matthias

      Comment

      • Stan Brown

        #4
        Re: What to use intead of taget_new in XHTML/Strict

        "chris Jangelov" <chris.jangelov @hemsidan.info> wrote in
        comp.infosystem s.www.authoring.html:[color=blue]
        >It seems that opening a link in a new window isn't considered to be good
        >practise in xhtml 1.1.[/color]

        Actually it's not considered to be good practice _on_the_Web_. It'
        just that later versions of HTML and XHTML enforce that.
        [color=blue]
        >Does anyone know what the proper solution would be to open a link in a new
        >window if I want all my pages to comply with the xhtml/strict level?[/color]

        You're asking what is the proper solution to have a red sofa that is
        blue. Your requirements are mutually contradictory. Either give up
        the idea of standard (X)HTML, or give up the idea of monkeying with
        the user's desktop.
        [color=blue]
        >I can see the thought behind, I think, but I would argue that there are
        >legitimate reasons for giving full control to the site I am linking to,
        >while my (unexperienced) visitor still doesn't loose track of my site.[/color]

        Translation: "My site is so important that stupid visitors who think
        they want to go somewhere else must have that made difficult for
        them." You're probably not thinking that, but that's the practical
        effect of what you're saying.

        --
        Stan Brown, Oak Road Systems, Tompkins County, New York, USA
        Dragon222 adalah situs slot gacor terbaru yang selalu memberikan banyak bonus menarik dan kemenangan JP untuk pemain setia selama bermain di link slot DRAGON222.

        HTML 4.01 spec: http://www.w3.org/TR/html401/
        validator: http://validator.w3.org/
        CSS 2 spec: http://www.w3.org/TR/REC-CSS2/
        2.1 changes: http://www.w3.org/TR/CSS21/changes.html
        validator: http://jigsaw.w3.org/css-validator/

        Comment

        • Neal

          #5
          Re: What to use intead of taget_new in XHTML/Strict

          On Mon, 19 Jul 2004 10:53:50 -0400, Stan Brown
          <the_stan_brown @fastmail.fm> wrote:
          [color=blue]
          > Translation: "My site is so important that stupid visitors who think
          > they want to go somewhere else must have that made difficult for
          > them." You're probably not thinking that, but that's the practical
          > effect of what you're saying.
          >[/color]
          What's more, many visitors won't even realize it's a new window, and when
          they try to use the Back button to return to your site, it won't work.

          Comment

          • Kris

            #6
            Re: What to use intead of taget_new in XHTML/Strict

            In article <42d12ec6.04071 90541.354f0b72@ posting.google. com>,
            chris.jangelov@ hemsidan.info (chris Jangelov) wrote:
            [color=blue]
            > I can see the thought behind, I think, but I would argue that there are
            > legitimate reasons for giving full control to the site I am linking to,
            > while my (unexperienced) visitor still doesn't loose track of my site.[/color]

            They don't. They have the back button if they need it, the number one
            button used by everyone. Besides, they decide to leave; howcome you
            think you can keep them on your site?

            --
            Kris
            <kristiaan@xs4a ll.netherlands> (nl)

            Comment

            • Shmuel (Seymour J.) Metz

              #7
              Re: What to use intead of taget_new in XHTML/Strict

              In <42d12ec6.04071 90541.354f0b72@ posting.google. com>, on 07/19/2004
              at 06:41 AM, chris.jangelov@ hemsidan.info (chris Jangelov) said:
              [color=blue]
              >Does anyone know what the proper solution would be to open a link in
              >a new window if I want all my pages to comply with the xhtml/strict
              >level?[/color]

              I'm not sure that there is a proper way to do it, because I'm not
              convinced that it is a proper thing to do.
              [color=blue]
              >I can see the thought behind, I think, but I would argue that there
              >are legitimate reasons for giving full control to the site I am
              >linking to, while my (unexperienced) visitor still doesn't loose
              >track of my site.[/color]

              You may run into browser that are configured to refuse to do what you
              want. It is the user that should have full control, not the site that
              you are linking to.

              --
              Shmuel (Seymour J.) Metz, SysProg and JOAT <http://patriot.net/~shmuel>

              Unsolicited bulk E-mail subject to legal action. I reserve the
              right to publicly post or ridicule any abusive E-mail. Reply to
              domain Patriot dot net user shmuel+news to contact me. Do not
              reply to spamtrap@librar y.lspace.org

              Comment

              • Andy Dingley

                #8
                Re: What to use intead of taget_new in XHTML/Strict

                chris.jangelov@ hemsidan.info (chris Jangelov) wrote in message news:<42d12ec6. 0407190541.354f 0b72@posting.go ogle.com>...
                [color=blue]
                > Does anyone know what the proper solution would be[/color]

                Use XHTML 1.0 Transitional.



                (Why use Strict ? WHy use 1.1 ?)

                Comment

                • Alan J. Flavell

                  #9
                  Re: What to use intead of taget_new in XHTML/Strict

                  On Tue, 20 Jul 2004, Andy Dingley wrote:
                  [color=blue]
                  > chris.jangelov@ hemsidan.info (chris Jangelov) wrote in message news:<42d12ec6. 0407190541.354f 0b72@posting.go ogle.com>...
                  >[color=green]
                  > > Does anyone know what the proper solution would be[/color]
                  >
                  > Use XHTML 1.0 Transitional.[/color]

                  That might be the answer to "Doctor, it hurts when I do this - how can
                  I continue doing it without it hurting too much?"
                  [color=blue]
                  > (Why use Strict ? WHy use 1.1 ?)[/color]

                  Good questions, indeed.

                  But why try to open new windows? If the user knows how to handle new
                  windows, they can do that for themselves. If they don't know, then
                  it's liable to confuse them (as well as being a WAI violation, if I'm
                  not mistaken).

                  Comment

                  • Andy Dingley

                    #10
                    Re: What to use intead of taget_new in XHTML/Strict

                    "Alan J. Flavell" <flavell@ph.gla .ac.uk> wrote in message news:<Pine.LNX. 4.53.0407201459 470.21802@ppepc 56.ph.gla.ac.uk >...
                    [color=blue]
                    > (as well as being a WAI violation, if I'm not mistaken).[/color]

                    Although there are plenty of people who think the WAI should be
                    violated with a pointy stick.

                    Comment

                    • chris Jangelov

                      #11
                      Re: What to use intead of taget_new in XHTML/Strict

                      "Alan J. Flavell" <flavell@ph.gla .ac.uk> wrote in message news:<Pine.LNX. 4.53.0407201459 470.21802@ppepc 56.ph.gla.ac.uk >...[color=blue]
                      > On Tue, 20 Jul 2004, Andy Dingley wrote:
                      >[color=green]
                      > > chris.jangelov@ hemsidan.info (chris Jangelov) wrote in message news:<42d12ec6. 0407190541.354f 0b72@posting.go ogle.com>...
                      > >[color=darkred]
                      > > > Does anyone know what the proper solution would be[/color]
                      > >
                      > > Use XHTML 1.0 Transitional.[/color]
                      >
                      > That might be the answer to "Doctor, it hurts when I do this - how can
                      > I continue doing it without it hurting too much?"
                      >[color=green]
                      > > (Why use Strict ? WHy use 1.1 ?)[/color]
                      >
                      > Good questions, indeed.
                      >
                      > But why try to open new windows? If the user knows how to handle new
                      > windows, they can do that for themselves. If they don't know, then
                      > it's liable to confuse them (as well as being a WAI violation, if I'm
                      > not mistaken).[/color]

                      Thank you all for your input.

                      I think I'll stick to the advice "use XHTML Transitional". This
                      complies with a standard, which I like, and still fulfill my needs.

                      I want to try 3 arguments for further discussion:

                      1: I am remaking a site about nordic ballads and we want to be a
                      center/ a hub
                      for the subject. That would mean linking to resouces wherever they are
                      rather than reinventing the wheel. A user behaviour cold be to browse
                      different sites from linklist at our site, and then they would like to
                      keep
                      our site as the steady bottom for that session.

                      2: I also think that hyperlinking to a photo as an illustration to a
                      text
                      is a reasonable approach. If we were to put all images in the document
                      that
                      would be an unnecessary bandwidth comsumer for many modem surfers.

                      3: One could also say that the problem arises because many browsers
                      aren't
                      tabbed. If one were to look att it as different windows/aspects of a
                      surf
                      trail, rather than new browser windows, it might just mean that the
                      strict
                      standard is a bit too narrow.

                      (I kind of like the last one :-)

                      /chris

                      Comment

                      • Jan Roland Eriksson

                        #12
                        Re: What to use intead of taget_new in XHTML/Strict

                        On 20 Jul 2004 12:03:41 -0700, chris.jangelov@ hemsidan.info (chris
                        Jangelov) wrote:

                        [...]
                        [color=blue]
                        >1: I am remaking a site about nordic ballads and we want to be a
                        >center/a hub for the subject. That would mean linking to resouces
                        >wherever they are rather than reinventing the wheel.
                        >A user behaviour cold be to browse different sites from linklist
                        >at our site, and then they would like to keep our site as the
                        >steady bottom for that session.[/color]

                        A simple case for the users "back" mechanism, whatever that might be.
                        Surely any www user knows how to get back from where s/he started, _if_
                        s/he is interested to go back in the first place.
                        [color=blue]
                        >2: I also think that hyperlinking to a photo as an illustration to
                        >a text is a reasonable approach. If we were to put all images in the
                        >document that would be an unnecessary bandwidth comsumer for many
                        >modem surfers.[/color]

                        Huh? what's wrong with a simple "Anchor" element when you need it?
                        [color=blue]
                        >3: One could also say that the problem arises because many browsers
                        >aren't tabbed.[/color]

                        No; if that is a "problem" in your view, you created it.
                        [color=blue]
                        >If one were to look att it as different windows/aspects of a
                        >surf trail, rather than new browser windows, it might just mean that
                        >the strict standard is a bit too narrow.[/color]

                        You are off base. The www is an area that lives inside and as a part of
                        internet. Internet is at large a "client/server" system where clients
                        are supposed to have full control over what they request as a service
                        from servers.

                        Forget this "I want to control users behavior" scenario because there is
                        in reailty _nothing_ you can do in what you serve that can "force" any
                        user out there to dance to your pipe.
                        [color=blue]
                        >(I kind of like the last one :-)[/color]

                        Maybe so; it's a faulty attitude to the i-net never the less.

                        --
                        Rex


                        Comment

                        • Shmuel (Seymour J.) Metz

                          #13
                          Re: What to use intead of taget_new in XHTML/Strict

                          In <42d12ec6.04072 01103.e1f4b40@p osting.google.c om>, on 07/20/2004
                          at 12:03 PM, chris.jangelov@ hemsidan.info (chris Jangelov) said:
                          [color=blue]
                          >I want to try 3 arguments for further discussion:[/color]

                          Frames.

                          --
                          Shmuel (Seymour J.) Metz, SysProg and JOAT <http://patriot.net/~shmuel>

                          Unsolicited bulk E-mail subject to legal action. I reserve the
                          right to publicly post or ridicule any abusive E-mail. Reply to
                          domain Patriot dot net user shmuel+news to contact me. Do not
                          reply to spamtrap@librar y.lspace.org

                          Comment

                          • Darin McGrew

                            #14
                            Re: What to use intead of taget_new in XHTML/Strict

                            Jakob Nielsen pointed out the fundamental problems with opening new windows
                            5 years ago. See item #2 at http://www.useit.com/alertbox/990530.html

                            The fundamental problems haven't changed in that time.

                            chris Jangelov <chris.jangelov @hemsidan.info> wrote:[color=blue]
                            > 1: I am remaking a site about nordic ballads and we want to be a
                            > center/ a hub
                            > for the subject. That would mean linking to resouces wherever they are
                            > rather than reinventing the wheel. A user behaviour cold be to browse
                            > different sites from linklist at our site, and then they would like to
                            > keep
                            > our site as the steady bottom for that session.[/color]

                            The "hub sites" that I use every day manage to do this without opening new
                            browser windows. If I want a new browser window, then I know how to open it
                            myself.

                            Users who don't know how to use basic functions of their browsers will only
                            be confused when various pages imitate those functions in different ways.
                            And yes, I've seen users who don't know how to use windows effectively get
                            confused when a browser opens one for them. "Why doesn't the back button
                            work?" is just one symptom, and ironically, it's the site that opened a new
                            window that they can't return to using the back button.
                            [color=blue]
                            > 2: I also think that hyperlinking to a photo as an illustration to a
                            > text
                            > is a reasonable approach. If we were to put all images in the document
                            > that
                            > would be an unnecessary bandwidth comsumer for many modem surfers.[/color]

                            Thumbnails work well. Or you can use text links. Regardless, if I want to
                            open a new window, I can. If I want to follow the link and then use the
                            back button, I can. It's better to let users work the way they want to
                            work, than to force them to work in a way they are unfamiliar with or
                            uncomfortable with.
                            [color=blue]
                            > 3: One could also say that the problem arises because many browsers
                            > aren't
                            > tabbed. If one were to look att it as different windows/aspects of a
                            > surf
                            > trail, rather than new browser windows, it might just mean that the
                            > strict
                            > standard is a bit too narrow.[/color]

                            That still doesn't justify taking away the user's choice over whether to
                            open a new link in the current window or in a new window. No matter how the
                            browser represents new windows (e.g., there are non-visual browsers that
                            support the concept of multiple "windows"), the creation of those new
                            windows should remain under the user's control.

                            When browsers include user-configuration settings that prevent documents
                            from controlling certain behaviors, it's probably a good idea for authors
                            to avoid trying to control those behaviors. Opera has 3 different settings
                            to subvert document-controlled new windows. I that understand Gecko- and
                            KHTML-based browsers offer similar settings. Who knows--the next version of
                            MSIE might even catch up.
                            --
                            Darin McGrew, mcgrew@stanford alumni.org, http://www.rahul.net/mcgrew/
                            Web Design Group, darin@htmlhelp. com, http://www.HTMLHelp.com/

                            "The handwriting on the wall may mean you need a notepad by the phone."

                            Comment

                            • Claire Tucker

                              #15
                              Re: What to use intead of taget_new in XHTML/Strict

                              On 20 Jul 2004 12:03:41 -0700, chris.jangelov@ hemsidan.info (chris
                              Jangelov) wrote:
                              [color=blue]
                              >1: I am remaking a site about nordic ballads and we want to be a
                              >center/ a hub
                              >for the subject. That would mean linking to resouces wherever they are
                              >rather than reinventing the wheel. A user behaviour cold be to browse
                              >different sites from linklist at our site, and then they would like to
                              >keep
                              >our site as the steady bottom for that session.[/color]

                              When I'm browsing and I encounter such a jump-off site, I generally
                              middle-mouse-click the links which, in my browser, opens the links in
                              a new tab. However, sometimes I use the jump-off site to find a
                              particular site I forgot the URL for, so I left-click the link because
                              I really don't care much for anything else on the jump-off site at
                              that point. If the site *still* opens in a new window, I'm going to
                              get very cross.

                              People who care about such things already know how to either open
                              links in new windows/tabs or use the back button. The few people who
                              don't know about one of these things will learn soon enough, and if
                              anything your attempt to force them to keep your site open will
                              probably make that learning process even longer and more frustrating
                              as the links on your site will act differently to the user has seen
                              links act on other sites.
                              [color=blue]
                              >3: One could also say that the problem arises because many browsers
                              >aren't tabbed.[/color]

                              Due to (IMHO, misplaced) backward-compatibility concerns even tabbed
                              browsers seem to open target="_blank" links in new windows (rather
                              than tabs) by default. This is quite frustrating, since the user must
                              then manually re-absorb this unwanted extra window back into the
                              original window where it belongs.

                              --------

                              My main argument against using target="_blank" (among many others) is
                              this:

                              If you don't specify the target, all browsers which support such
                              things give the user a choice between new window or current window
                              and, in newer browsers, new tab as well.

                              If you specify target="_blank" , you eliminate the "open in current
                              window" option, so the user now has a choice between "open in a new
                              window that I don't want", "open in a new window that I do want" and
                              maybe "open in a new tab", although the last option might also be
                              broken by your misplaced attempt to boss the user around.

                              Have a good think about this and hopefully you'll realise that what
                              you are trying to do is a bad idea and was deprecated for a reason.

                              Best regards,
                              -Claire

                              Comment

                              Working...