Sea Monkey–new release

Forum Forums New users New Users and General Questions Sea Monkey–new release

  • This topic has 18 replies, 8 voices, and was last updated Sep 6-7:01 pm by Brian Masinick.
Viewing 4 posts - 16 through 19 (of 19 total)
  • Author
    Posts
  • #66570
    Moderator
    Brian Masinick
      Helpful
      Up
      0
      ::

      Palemoon, current version, performs the test exactly the same as Seamonkey 2.53.9, only passes one test.
      Firefox 88 does a bit better, I’ll check the current, beta, and Nightly versions of Firefox; expect a better result, will confirm one way or the other.

      --
      Brian Masinick

      #66571
      Moderator
      Brian Masinick
        Helpful
        Up
        0
        ::

        Firefox 91.0.2 fails two tests. (Check ’em yourselves to see which tests pass and fail).

        --
        Brian Masinick

        #66572
        Anonymous
          Helpful
          Up
          0
          ::

          > Just out of curiosity

          The reason I mentioned it:

          https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP
          (page Last Modified Aug 30, 2021)

          A SPECIFIC INCOMPATIBILITY EXISTS IN SOME VERSIONS OF THE [SAFARI] WEB BROWSER, WHEREBY IF A CONTENT SECURITY POLICY HEADER IS SET, BUT NOT A SAME ORIGIN HEADER, THE BROWSER WILL BLOCK SELF-HOSTED CONTENT AND OFF-SITE CONTENT, AND INCORRECTLY REPORT [naw, it is SILENT unless user opens a WebInspector pane] THAT THIS IS DUE TO THE CONTENT SECURITY POLICY NOT ALLOWING THE CONTENT.

          I have adopted a habit of citing links to github / gitlab antiX project repo pages within my posts, but I now suspect the “incompatibility” mentioned above is not specific to Safari… and that the project repo pages will not render properly if/when a SeaMonkey user visits those pages.

          #66574
          Moderator
          Brian Masinick
            Helpful
            Up
            0
            ::

            Thanks for the reference skidoo; based on the table in the reference I can see why and where Firefox, Palemoon, and Seamonkey (as configured straight from installation) do NOT pass 100% of the tests.

            I didn’t study the table in depth to ascertain whether any of these browsers could be configured (in about:config) without having to modify the sources, (which would clearly be impractical, difficult, and probably not possible for 99% of us (I am definitely not up to the task!).

            Nevertheless this is interesting because it indicates areas where all of the current generation of Web browsers are not 100% in sync with the recommendations of the reference.

            --
            Brian Masinick

          Viewing 4 posts - 16 through 19 (of 19 total)
          • You must be logged in to reply to this topic.