Thanks for the report.

Able to reproduce this issue on Mac OS 10.13.3 on the latest Canary 69.0.3482.0 and Beta 68.0.3440.42 by enabling the flag #views-browser-windows.
Issue is not applicable to Windows 10 and Ubuntu 14.04.

Bisect Information:
===================
Good Build: 68.0.3431.0
Bad Build : 68.0.3432.0

By running the per-revision bisect script, float division by zero error was coming up. Hence below is the manual changelog URL from omahaproxy.

https://chromium.googlesource.com/chromium/src/+log/68.0.3431.0..68.0.3432.0?pretty=fuller&n=10000

From the above Changelog, suspecting the below change:
Reviewed-on: https://chromium-review.googlesource.com/1056468

spqchan@ Please check and confirm if this issue is related to your change, else help us in assigning to the right owner.
Adding 'ReleaseBlock-Stable' label as this is a recent regression. Please feel free to remove if this is not applicable.

Thanks

Please reconfirm with new native context menus on canary after July 13.

Unable to reproduce the issue on mac 10.13.5 using latest chrome version #69.0.3493.0.

Attached a screen cast for reference.

Following are the steps followed to reproduce the issue.
------------
1. Launched chrome using chrome://flagsNavigated to Help > Report an Issue...
2. Right-clicked any area that is not a text input field
3. Observed that context menu did not pop up with single string "(empty)"

As we are unable to reproduce the issue from our end. Hence, removing Needs-TestConfirmation label.

Thanks...!!

Deleted: 859773.mp4 551 KB

	859773.mp4 551 KB View Download

Can't repro with the native context menu change.