GleamTech.FileUltimate 9.0.3

• .NETFramework 4.7.2

  • GleamTech.Common (>= 6.0.6)
  • GleamTech.DocumentUltimate (>= 7.0.9)
  • GleamTech.ImageUltimate (>= 6.0.0)
  • GleamTech.VideoUltimate (>= 4.0.0)

• .NETStandard 2.0

  • GleamTech.Common (>= 6.0.6)
  • GleamTech.DocumentUltimate (>= 7.0.9)
  • GleamTech.ImageUltimate (>= 6.0.0)
  • GleamTech.VideoUltimate (>= 4.0.0)

## Version 9.0.3 - August 2, 2024

 - **Improved:** Added EscapeClosingScriptTags method to RazorPageExtensions, WebViewPageExtensions and WebPageExtensions
   which escapes closing script tags, i.e. replaces `</script>` with `<\/script>`.
   
   When you render a component inside a `<script>` tag, for example when you set a javascript variable to
   the result of inline @RenderHead or @RenderBody calls, the result may contain closing `</script>` tags
   and browser treats these tags as an immediate stop even if they are enclosed in a javascript string literal:

   ```html
   <script>
      //this will fail in browser because there are closing `</script>` tags in the rendered result.
      var html = `@this.RenderBody(component)`;
   </script>
   ```
   
   So to prevent the issue, escape closing script tags when you are inside `<script>` tag, with this method:
   ```html
   <script>
      var html = `@this.RenderBody(component).EscapeClosingScriptTags()`;
   </script>
   ```

   Details: The browser finds the </script> piece in the string and thinks that it is the closing tag
   of the first script element. It treats the rest of the script and the real </script> closing tag as regular text
   and displays it in the page (except for the </script> tag).