BUG in Context Menu copy reference as Search content.

For each entry type in the Bible Browser, I did the following:

selected a random value for some attribute under the facet
selected an appropriate portion of one of the results displayed
used right-click to open the context menu
selected the datatype or label that represented the facet I'd selected
selected "search' in the copy reference option
pasted that result into a table included in my post for today's tip.

INCONSISTENCY/BUG:

<LiteraryTyping ~ Healing> was the only item requiring {Section } that was not wrapped in that extension. I know that Bradley has indicated he'd rather none of them were wrapped. My concern is simply that they be predictable i.e. consistent. (I do prefer they be wrapped in the extension but I understand why Bradley holds his position).

Find more posts tagged with

Desktop App

Comments

MJ. Smith

bump for visibility 14

Dave Hooton

<LiteraryTyping ~ Healing> was the only item requiring {Section } that was not wrapped in that extension.

<Topic ...> also requires the extension. But some datatypes have both Search terms e.g. <PreachingTheme...> and the extension. So I'm not so understanding when a result requires the extension.

MJ. Smith

By "require" I mean that the bare datatype will return no results in a basic search against all resources and that when wrapped in the extension, it will return results.