200 X-Frame-Options: SAMEORIGIN Content-Security-Policy: frame-ancestors 'self'; X-UA-Compatible: IE=Edge X-XSS-Protection: 1; mode=block X-Content-Type-Options: nosniff X-Telligent-Evolution: 12.x Pragma: no-cache Connection: close Accept-Ranges: bytes Cache-Control: no-store, no-cache, max-age=0 Date: Sat, 30 Nov 2024 16:35:38 GMT ETag: "0x8DD02F56CCD7D1F" Set-Cookie: .te.csrf=JfgQGLK6IXpKyBTVgTI8N_l8XcvX54og9TdWJs1bikk; path=/; secure; SameSite=Lax Set-Cookie: .te.auth=MenlY94zU%2bJExVu4z1p5W6RmXjmO0qyWnsarC88f4DxPXGn%2bEcMBDfUZ82%2fUdyLrNXanZsuu4WoexdZsUBbigHZr6aRSUCPavRzNU1B4dKUdR210AClSX%2fFS5D9U3mhAY6uQW4HXqnNRd%2f05B%2bTMMJ4nOrpvZYHos4tRSfUAx5ePEKpXbv0Eq7TFOXcTBTovgair6sWG0OO4nSp%2feIwRQbRdqZ%2b97hWtYWjzbZNTPFjfL5TQ7zuCSmP4T%2bw1V0LsNmptkQc4oz7joY%2bvkzhJ%2bA%3d%3d; path=/; secure; HttpOnly; SameSite=Lax Set-Cookie: e14Guest=1; expires=Fri, 31-Dec-9999 23:59:59 GMT; path=/; secure; HttpOnly Set-Cookie: e14Country=NL; expires=Fri, 31-Dec-9999 23:59:59 GMT; path=/; secure; HttpOnly Set-Cookie: e14Language=en; expires=Fri, 31-Dec-9999 23:59:59 GMT; path=/; secure; HttpOnly Set-Cookie: e14TimeZone=Etc/UTC; expires=Fri, 31-Dec-9999 23:59:59 GMT; path=/; secure; HttpOnly Server-Timing: cdn-cache; desc=MISS Server-Timing: edge; dur=8 Server-Timing: origin; dur=27 Server-Timing: ak_p; desc="1732984538819_34849654_156193792_3507_8670_4_6_-";dur=1 Strict-Transport-Security: max-age=86400 ; includeSubDomains ; preload #set ($UserId = $core_v2_user.Accessing.Id) #set ($Roles = $core_v2_utility.MakeList('Moderators', 'Almost Admins', 'Administrators')) #set ($IsAdminLike = $e14_utils.IsUserInRoleOrAdmin($UserId, $Roles)) #if($IsAdminLike == 'False') #end
Actions
Forum Thread Details
  • State Verified Answer
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 12 subscribers
  • Views 4564 views
  • Users 0 members are here
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Problem with creating blogs with Edge

jc2048

In the last couple of days my Microsoft Edge browser has stopped being able to present the blog editing screen correctly. It ends up like this, without menus and tool buttons. Initially, it seems that it paints the usual screen (bit difficult to tell because it's just a momentary flash in front of the eyes), then immediately repaints it with this one where the 'Body' box just shows two lines.

image

Edge version is 102.0.1245.39 64-bit on Win 8.1. It says it's up to date.
There was an upgrade earlier this week (it resulted in one of those splash screens that tell you about all the wonderful new features, so it was more than just bug fixes), so it might have been that that brought the change.

Has anyone else had a similar problem using Edge?

Any thoughts on what the problem might be and whether there's anything I can do to get it back?

I'm posting this using Sea Monkey (based on Mozilla), which is fine with the editing so it doesn't stop me contributing, but it's more sluggish than Edge and I'd like to continue with using Edge if I could.

Parents
  • 0

    At least I can directly comment about this problem, because I solely use Microsoft Edge when creating content on the Community.

    I'm using 

    Version 102.0.1245.39 (Official build) (64-bit)
    on Windows 10. 
    The problem you're experiencing is when the page doesn't fully load. I briefly see it before everything on the page fully appears.
    If you can look in the 'dev tools' on the page, and let me know if there're any errors in the console and what they are, then that would help. Along with what date and time of day you're experiencing the problem. 
  • 0 in reply to cstanton

    Will this do (the screengrab, I mean - I couldn't quickly see how to save the console as a file)?

    image

    It looks like it might be something related to tracking options in the browser.

    That was today and a few minutes ago.

  • +1 in reply to jc2048
    jc2048 said:
    I couldn't quickly see how to save the console as a file)?

    Right-click -> context menu -> save as...

    The tracking options are unrelated, there's currently an error with google analytics not loading properly.

    The actual error there is the 503 on tinymce.min.js - that's the javascript for the TinyMCE editor which is all of the javascript features to give you a fully fleshed out blog editor.

    This is helpful.

    Have you tried clearing your browser cache?

Reply
  • +1 in reply to jc2048
    jc2048 said:
    I couldn't quickly see how to save the console as a file)?

    Right-click -> context menu -> save as...

    The tracking options are unrelated, there's currently an error with google analytics not loading properly.

    The actual error there is the 503 on tinymce.min.js - that's the javascript for the TinyMCE editor which is all of the javascript features to give you a fully fleshed out blog editor.

    This is helpful.

    Have you tried clearing your browser cache?

Children