<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p>How about my suggestion above?<br>
      Why won't anyone comment on my suggestion above?</p>
    <p>If no one comments I won't be able to understand if I made a
      mistake or not...<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 22/02/2017 10:39, Till Schneidereit
      wrote:<br>
    </div>
    <blockquote
cite="mid:CACRHVk_RcT_txj+u652Wh3y3GiU6pQ+Y=xYaCBi0PQCaDeAz_w@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">On Tue, Feb 21, 2017 at 8:15 PM, Gijs
            Kruitbosch <span dir="ltr"><<a moz-do-not-send="true"
                href="mailto:gijskruitbosch@gmail.com" target="_blank">gijskruitbosch@gmail.com</a>></span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div bgcolor="#FFFFFF" text="#000000">
                <div class="m_-1916897508278880903moz-cite-prefix">While
                  we *might* be able to have a reasonable idea (and this
                  really isn't trivial - see Bill's message, but also
                  think of how we sometimes show the 'slow script'
                  dialog and point to the wrong code as being slow), I
                  think it's highly unlikely we'll ever be confident
                  enough to inadvertently uncheck the suspected tab
                  automatically, thus basically destroying user data
                  (including the back/forward history of that tab, form
                  data, cookies, scroll positions - everything) in case
                  we're wrong.<br>
                  <br>
                  Even if we tell the user this, that treeview is a pain
                  to use, and it's very likely that unchecked tabs will
                  be scrolled out of view in some cases. We know that
                  users don't read long descriptive text. So we
                  effectively show a page with a big highlighted button
                  to restore everything - and then we restore everything
                  except some of them, with no way for users to get
                  those items back. That sounds like a terrible
                  experience to me.<br>
                </div>
              </div>
            </blockquote>
            <div><br>
            </div>
            <div>Could we perhaps instead of showing this page at all
              replace the suspect tab(s) with a "we think this page
              might've caused the last crash, <click here> if you
              still want to restore it" page? Perhaps combined with a
              notification bar indicating that not all tabs were
              restored normally.<br>
            </div>
          </div>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
firefox-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:firefox-dev@mozilla.org">firefox-dev@mozilla.org</a>
<a class="moz-txt-link-freetext" href="https://mail.mozilla.org/listinfo/firefox-dev">https://mail.mozilla.org/listinfo/firefox-dev</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>