sodcalculator

10 Tech How-To

How to Test Websites on Microsoft Edge 79 and macOS Catalina

Guide 10-45644 · Updated · Step by step

Testing websites on Microsoft Edge 79 and macOS Catalina lets you verify how your site renders in the Chromium-based Edge browser on a Mac, ensuring compatibility for users on that combination. This guide walks you through setting up Edge 79 on Catalina, using its built-in developer tools, and running practical tests for layout, responsiveness, and performance. You’ll need a Mac running macOS Catalina (10.15) and an internet connection to download the installer.

What You’ll Need

  • A Mac running macOS Catalina (10.15) or later (Edge 79 supports 10.13+).
  • An administrator account to install software.
  • The URL of the website you want to test.
  • Optional: a second device or browser for cross-checking.

Step-by-Step

  1. Download Microsoft Edge 79 – Open Safari (or any browser) and go to the official Microsoft Edge download page. Select the macOS version (the .pkg file). If you need the exact 79 build, look for the “Enterprise” or “Previous versions” section on Microsoft’s site, as the consumer page usually offers the latest version.
  2. Install Edge 79 – Once the .pkg downloads, double-click it to open the installer. Follow the prompts, enter your admin password when asked, and allow the installation to complete. After it finishes, you may be asked to move Edge to the Applications folder (do that for easier access).
  3. Launch Edge and set up a test profile – Open Edge from the Applications folder. On first launch, it will ask about importing data and signing in. For testing, create a separate profile: click the profile icon (top right), then “Add profile” and choose “Add” without signing in. This keeps your testing environment clean.
  4. Open your website – In the address bar, type the full URL (e.g., https://example.com) and press Enter. Wait for the page to fully load.
  5. Open Developer Tools – Press F12 (on a Mac, you may need Fn+F12) or go to the menu: View → Developer → Developer Tools. Alternatively, right-click anywhere on the page and select “Inspect”. This opens a panel at the bottom or side of the window.
  6. Check the Console for errors – Click the “Console” tab in DevTools. Look for red error messages (JavaScript errors, network failures, or security warnings). Note any messages that appear, as they can break functionality.
  7. Test responsiveness with Device Toolbar – Click the “Toggle device toolbar” icon (a small rectangle with a phone outline) in the DevTools top-left corner. This simulates mobile and tablet viewports. Select a device like “iPhone 11” or “iPad” from the dropdown, or set a custom width/height. Scroll through the page to see how layout, images, and menus behave.
  8. Inspect and edit CSS live – Click the “Elements” tab. Select any element on the page to see its CSS rules in the right sidebar. You can toggle styles off/on or change values (like font-size) to see how the page responds instantly. This helps identify styling issues without editing your source code.
  9. Test network performance – Go to the “Network” tab and reload the page (Cmd+Shift+R for hard reload). You’ll see a list of all resources loaded (scripts, images, stylesheets). Check for any that fail (red status) or take too long. Use the “Throttling” dropdown to simulate slower connections (e.g., “Fast 3G”) and see how the site performs.
  10. Verify browser compatibility features – In the DevTools, click the three-dot menu (⋮) and select “More tools” → “Coverage”. Click the record button and reload the page. This shows which CSS/JS is actually used. Also, check the “Rendering” tab (via the same menu) to see “Emulate CSS media feature prefers-color-scheme” – test both light and dark modes if your site supports them.
  11. Test with Edge’s built-in screenshot tools – In the device toolbar, click the “Screenshot” icon (camera) to capture a full-page screenshot of the current viewport. This is useful for documenting issues or sharing with your team.
  12. Check for mixed content or security warnings – Look at the address bar for any warning icons (like a lock with a slash). Click on them to see details. Also, in the Console, watch for “Mixed Content” errors – these occur when a secure HTTPS page loads insecure HTTP resources, which Edge blocks by default.
  13. Test keyboard navigation and accessibility – Tab through the page to ensure focus order is logical. Use the DevTools “Accessibility” tab (under Elements when an element is selected) to inspect ARIA attributes and contrast ratios. This is a quick check for basic accessibility.
  14. Save your test results – Use the “Export” feature in the Network panel (right-click a request → “Save all as HAR”) to save a performance log. For visual issues, take screenshots (Cmd+Shift+4 on the Mac) and annotate them.

Common Mistakes

  • Using the wrong Edge version – If you install the latest Edge, you’re not testing 79. Always verify the version via the menu: Edge → About Microsoft Edge. If you need 79 specifically, download it from the official “Previous versions” page.
  • Forgetting to clear cache – Edge caches resources aggressively. When testing changes, use Cmd+Shift+R to hard reload, or clear the cache via Settings → Privacy → Clear browsing data.
  • Testing only in a maximized window – Real users have varied window sizes. Use the device toolbar to test at common resolutions (1366×768, 1920×1080) and not just your screen size.
  • Ignoring the console – Many layout issues are caused by JavaScript errors. Always check the Console first – a single error can break an entire script.
  • Not testing with a clean profile – Extensions or saved logins can alter behavior. Use a separate test profile to avoid false positives.

Tips

  • Use Edge’s “InPrivate” window – Open a new InPrivate window (Cmd+Shift+N) to test without extensions or cache, simulating a fresh visit.
  • Leverage the “Sensors” tool – In DevTools, under “More tools” → “Sensors”, you can override geolocation and device orientation to test location-based features.
  • Check for WebKit-specific issues – Since Edge 79 is Chromium-based, it may behave differently from Safari. If your site works in Safari but not Edge, compare the two using the same DevTools techniques.
  • Use the “Rendering” tab to simulate print media – Under “Emulate CSS media”, choose “print” to see how your print stylesheet works without actually printing.
  • Automate with PowerShell or AppleScript – For repeated tests, you can use AppleScript to control Edge (e.g., open a URL and take a screenshot) but for most manual testing, the steps above suffice.

Troubleshooting

  • Edge won’t install on Catalina – Ensure you have the correct .pkg file (not the Windows .exe). If the installer fails, try downloading again, or check that your Mac meets the minimum requirements (macOS 10.13+). Restart your Mac and try again.
  • Edge 79 is not available for download – Microsoft may have removed older versions from the main site. Use the “Enterprise” download page or a trusted third-party archive (be cautious). Alternatively, use the current Edge but note that differences are minimal for most testing.
  • DevTools don’t open – On some Mac keyboards, F12 is mapped to volume up. Use Cmd+Option+I instead, or go to View → Developer → Developer Tools.
  • Website looks fine in Safari but broken in Edge – Check the Console for vendor-prefix warnings (e.g., -webkit-). Use the “Elements” panel to see which CSS rules are being applied. Also, check the “Network” tab for failed resources that might be due to browser-specific request headers.
  • Edge crashes during testing – This could be due to a memory leak or a problematic extension. Try disabling extensions (Settings → Extensions) and test again. Also, ensure your Mac has enough free storage and RAM.
  • Cannot see the device toolbar – Click the “Toggle device toolbar” icon again – it might be hidden behind the panel. If not, reset DevTools settings via the gear icon → “Restore defaults”.

Frequently Asked Questions

Is Edge 79 the same as the current Edge?

No. Edge 79 was the first stable version based on Chromium, released in January 2020. The current Edge has many updates and new features, but the core rendering engine is still Chromium, so most testing principles apply.

Do I need to install Edge 79 specifically?

Only if you need to replicate the exact environment of a user who hasn’t updated. For most modern web development, testing on the latest Edge is sufficient, but if you have a specific bug report from Edge 79, it’s worth testing on that version.

Can I test Edge 79 on a newer macOS?

Yes, Edge 79 should run on macOS Big Sur and later, but you may encounter compatibility warnings. For best results, use a virtual machine or an older Mac if you need a pure Catalina environment.

How do I clear the cache in Edge on Mac?

Go to Settings → Privacy, search, and services → Clear browsing data. Choose “Cached images and files” and click “Clear now”. Or use Cmd+Shift+R for a hard reload.

Does Edge 79 support all modern CSS features?

Edge 79 is based on Chromium 79, so it supports most CSS features from that era, including Flexbox, Grid, and CSS variables. However, some newer features (like :is() or container queries) are not supported. Use Can I Use (caniuse.com) to check specific features.

Can I use Chrome DevTools shortcuts in Edge?

Yes, because Edge DevTools is based on Chromium, most shortcuts are identical (e.g., Cmd+Option+I for DevTools, Cmd+Shift+R for hard reload).

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →