E-mail List Archives
Re: Associating Errors From Wave Plug-in to the HTML Source
From: Jared Smith
Date: Dec 30, 2018 4:38PM
- Next message: JP Jamous: "Re: Associating Errors From Wave Plug-in to the HTML Source"
- Previous message: Jonathan Cohn: "Re: angular material datepicker and accessibility"
- Next message in Thread: JP Jamous: "Re: Associating Errors From Wave Plug-in to the HTML Source"
- Previous message in Thread: KellyFord: "Re: Associating Errors From Wave Plug-in to the HTML Source"
- View all messages in this Thread
> Is it possible to have the WAVE icon show up in the Chrome context menu or
> is that a browser restriction?
It is already. Just ensure that you don't have anything selected
within the page and the "WAVE this page" item should appear in the
context menu. There is also a default shortcut key of Control + Shift
+ U (Command + Shift + U on Mac). If this doesn't work, it may need to
be defined in the Keyboard Shortcuts settings for Extensions (also
available at chrome://extensions/shortcuts).
> Secondly, is it possible to have the WAVE extension results load in a new
> browser tab?
This isn't optimal because in many cases you may want to evaluate a
dynamic state of the page, and re-loading the page in a new tab would
negate this. You can, however, duplicate the tab (there is an option
for Duplicate in the Window menu) and then run WAVE there. I will,
however, look into an option for doing this automatically with the
WAVE extension in cases where this functionality is desired.
Thanks,
Jared
- Next message: JP Jamous: "Re: Associating Errors From Wave Plug-in to the HTML Source"
- Previous message: Jonathan Cohn: "Re: angular material datepicker and accessibility"
- Next message in Thread: JP Jamous: "Re: Associating Errors From Wave Plug-in to the HTML Source"
- Previous message in Thread: KellyFord: "Re: Associating Errors From Wave Plug-in to the HTML Source"
- View all messages in this Thread