Just like the racks of backup tapes that never get tested, I've just found that the CHM files my dev system has been dutifully building are empty. Once I get that resolved, I'll try upping the IE level in https://gitlab.com/wireshark/wireshark/-/blob/master/docbook/custom_layer_chm.xsl .
Another option is to change the href target: <p>See <a class="ulink" href=" https://gitlab.com/wireshark/wireshark/-/wikis/VOIPProtocolFamily"; target="_blank">VOIPProtocolFamily</a> for an overview of the used VoIP protocols.</p> Changing target="_top" to target="_blank" opens the link in a default browser window (or additional tab if already open). Works great but not sure if it reopens https://gitlab.com/wireshark/wireshark/-/issues/15860 On Wed, May 26, 2021 at 4:30 PM Gerald Combs <ger...@wireshark.org> wrote: > I think the only advantage that HTML Help offers at this point is the > ability to search for keywords. It otherwise adds a build requirement which > results in shipping a different help format on Windows, and the HTML Help > Viewer seems to behave worse as time goes on. I'd be OK with switching to > plain HTML. > > > On 5/26/21 12:28 PM, Graham Bloice wrote: > > Personally I prefer help to be local and not require internet access, > and I despise those local help abominations that spew hundreds of html > files into the filesystem. > > > > Not sure what's up with the links, maybe we need to make them pass off > to the system default browser rather than trying to render them in the HTML > help browser. > > > > On Wed, 26 May 2021 at 18:02, chuck c <bubbas...@gmail.com <mailto: > bubbas...@gmail.com>> wrote: > > > > https://www.wireshark.org/lists/wireshark-dev/200701/msg00396.html < > https://www.wireshark.org/lists/wireshark-dev/200701/msg00396.html> > > > > "Pressing the help button will: > > - on Win32 only: if available, open the Windows Help viewer with > locally installed user-guide.chm file - and if that fails ... - on all > systems: start a web browser and open the corresponding wireshark.org < > http://wireshark.org> online page" > > > > Clicking links in Windows HTML Help viewer is painful (and a little > unnerving) with script errors. > > > > Is it time to sunset and have Windows help act like non-Windows > platforms? > > Or maybe add a step to the CHM build process that makes the links > non-clickable so the user would need to copy/paste into a browser? > > > > chuckc > > > > > ___________________________________________________________________________ > > Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org > <mailto:wireshark-dev@wireshark.org>> > > Archives: https://www.wireshark.org/lists/wireshark-dev < > https://www.wireshark.org/lists/wireshark-dev> > > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > <https://www.wireshark.org/mailman/options/wireshark-dev> > > mailto:wireshark-dev-requ...@wireshark.org <mailto: > wireshark-dev-requ...@wireshark.org>?subject=unsubscribe > > > > > > > > -- > > Graham Bloice > > > > > ___________________________________________________________________________ > > Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> > > Archives: https://www.wireshark.org/lists/wireshark-dev > > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > > mailto:wireshark-dev-requ...@wireshark.org > ?subject=unsubscribe > > > > ___________________________________________________________________________ > Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> > Archives: https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org > ?subject=unsubscribe >
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
