5

Steps to reproduce:

  1. Visit https://www.linkedin.com/ and log in.
  2. Perform an action that will open a dialog, such as editing an entry in your profile.
  3. Notice that the screen is dimmed, without showing any dialog until the page is refreshed.

The issue is frequent but occurs inconsistently.
The issue also occurs in compatibility mode.
I couldn't reproduce the issue in Safari.

Expected behavior:

Dialogs are displayed without having to refresh the page.

Orion, OS version; hardware type:

Orion 0.99.122-beta (WebKit 615.1.11.7)
macOS 13.1
MacBook Pro M1

  • Vlad replied to this.

    This same issue happens when trying to connect with someone on linkedin. you click "connect" the screen dims and you aren't able to send the request. refreshing doesn't change the outcome no matter how many times you try it. fully bricked.

    Vlad

        Unfortunately I dont have LinkedIN so can not verify if current RC fixes it. Stay patient few more days...

          Vlad Sounds good Vlad. not stressing just wanted to bring it up to the team so they also know its not just an isolated issue.

              15 days later

              I have the same setup and problem. I notice the console shows a lot of
              Failed to load resource: the server responded with a status of 404 ()
              for *.map files from https://static.licdn.com/

                I think manually visiting https://static.licdn.com and disabling content blocking through the Website Settings helps.

                  Just visit https://static.licdn.com and click this icon.

                  I think I spoke too soon, though; I still have problems with dialogs. It might be related to
                  Unhandled Promise Rejection: TypeError: undefined is not a function (near '...[n,i,a]...')
                  in relation to L17226 of this code:
                  ... if(i)throw e}const d=[t.IS_BROWSER?"browser":"bpr"]

                    emre I just tried and it looks like I am up and running but I will report back if I hit an obstacle.

                        5 days later

                        Another error I just saw is

                        The Content Security Policy 'default-src 'none'; base-uri 'self'; form-action 'self'; connect-src 'self' blob: wss: *.licdn.com *.linkedin.com; img-src 'self' blob: data: *.licdn.com *.linkedin.com; font-src data: *; frame-src 'self' blob: lnkd-communities: voyager: *.licdn.com *.linkedin.com; child-src 'self' blob:; worker-src 'self' blob:; style-src 'self' 'unsafe-inline' *.licdn.com *.linkedin.com; media-src 'self' blob: data: *.licdn.com *.linkedin.com; manifest-src 'self'; script-src 'unsafe-eval' 'unsafe-inline' *.licdn.com *.linkedin.com' was delivered in report-only mode, but does not specify a 'report-to'; the policy will have no effect. Please either add a 'report-to' directive, or deliver the policy via the 'Content-Security-Policy' header.

                        @Vlad could you create a test account for LI?

                          emre I prefer not to, it smells like a WebKit issue though and should be fixed with the next WebKit update.

                              emre I did the previous fix you suggested and I am having around a 99% success rate with the problem being fixed.

                                The Version 0.99.123.1-beta (WebKit 615.1.16.1) update on Feb. 3 seems to have resolved the issue.

                                No one is typing