Wp-calypso: Can't access My Site in Microsoft Edge/IE11 on Windows (new single site user)

Created on 26 Apr 2017  路  6Comments  路  Source: Automattic/wp-calypso

Steps to reproduce

  1. Starting at URL: https://wordpress.com/start on Microsoft Edge or IE11
  2. Sign up for a free site
  3. Once signed up, visit wordpress.com and click "My Site"

What I expected

Dashboard (stats)

What happened instead

Blank page

Console error:
Unable to get property 'getHostNode' of undefined or null reference

Browser / OS version

Microsoft Edge 38.14393.0.0 (Windows 10)

Screenshot / Video

Edge:

edge

IE11

ie11

NUX Site Picker Sites [Pri] High [Type] Bug

Most helpful comment

Thanks for the fix, retested my steps in MS Edge and can no longer reproduce this bug.

All 6 comments

This may have been introduced in #13196

cc: @ockham

This is possibly not IE specific. Trying this locally from up-to-date master (to see more console errors), I'm getting

image

@alisterscott Can you repro that?

Tested with Edge 14 (Microsoft Edge 38.14393.0.0 and EdgeHTML 14.14393) on Windows 10 for a brand new user sign up starting at https://wordpress.com/start and was also unable to reproduce the problem:

screen shot 2017-04-26 at wed apr 26 9 18 02 am
Seen at https://wordpress.com/stats/day/madefortesting455.wordpress.com using Edge 14 on Win10.

Also tested with Edge 14 (Microsoft Edge 38.14393.0.0 and EdgeHTML 14.14393) on Windows 10 with an already-existing account on production and didn't find any problems (note: this account did have a personal plan so may not have been a good test case judging from the stack trace in the previous comment). I did see several 404 errors for .scss files on widgets.wp.com:

bs_win10_edge_14 0_170426
Seen at https://wordpress.com/stats/day/madefortesting532.wordpress.com using Edge 14 on Win10.

Yeah, this kind of issue is quite hard to repro. I'm pretty sure now the culprit is this line, so I'll modify #13409 to guard against falsey site.

I can repro with steps:
1) logged out, go to https://wordpress.com/themes
2) sign in with an existing single-site user

Thanks for the fix, retested my steps in MS Edge and can no longer reproduce this bug.

Was this page helpful?
0 / 5 - 0 ratings