DocuSign | Anchor Tags - json

If we are to define an anchor tags and want it to be invisible, I know we can just copy the background as the guide says (https://developers.docusign.com/docs/esign-rest-api/esign101/concepts/tabs/auto-place/). But, is anyone familiar, what if the anchor tags \test\ is in two different colors? Can we cater that?
Or the options are to:
Trim the anchor tags.
Move the anchor tags in one color and just use xoffset/yoffset?

Font color has no bearing on searching for the anchor text and processing tab placement.

Related

Make elements that behave like anchor tags?

I was wondering, can you make an element that is not an anchor (<a>) tag (for ex. <div>, <span>, etc.) behave like an anchor tag? (Link to page on click).
Or, are there any other elements that behave the same?
Only partially.
You can give any tag a tabindex to make it focusable.
You can give any tag a click event listener that sets location.href.
You can't make anything other than a real link react to :link and :visited in CSS
That leaves aside issues of getting (for example) screen readers to recognise the element as a link and annouce it to the user, and for search engines to recognize it as a link and follow it, and the JS simply failing.
In short: If you want a link, then use a real link. HTML is a semantic markup language. Use the semantics it comes with. Don't try to fake the behaviour that comes with the semantics using other elements.

Why can't you use href in an <o> or <k> tag?

So I found out recently that just like
<p> and <a>
you can use your own like
<o> and <k>
and style them in a css sheet by just using
o {} and k {}
which is pretty cool but unlike
<a> which you can href to
you can't do this with
<o> because <o href="url"></o> just doesn't work, even when adding the styling for cursor hover and o:focus {etc..} and o:hover {etc..}
Could anyone explain why? I got around it by using spans but it would be cool to be able to use any combination of letters for custom tags which have href functionality
Stay away from defining your own tags. XML offers users the ability to define their own tags, while HTML (especially HTML5) wants the user to use the pre-defined tags consistently.
The reason why you can't use href on just anything you like is because HTML just doesn't allow it. You use <a>s when placing links, <span>s to style certain word(s) of a text.
http://www.w3schools.com/tags/tag_span.asp
For the simple reason that if you define a "custom" element like this:
<o href="url">go to page x</o>
you probably mean a behavior like this:
go to page x
But what we are "supposing" can't be simply "predicted" by the browser; so, basically, the browser wouldn't know how to manage those attributes which you are giving to your custom tag...
Indeed, when you use something like <o>...</o> "tag" you are NOT defining a REAL custom tag; you are just placing a markup: whose regard the browser is simply "trasparent" (indeed doesn't do anything) just shows what is inside (if "showable") as if the "custom tag" wasn't there (we might say a "null" inline element). It can be managed, of course, trought CSS and Javascript that will specify the rest...
To build a real custom element you should place it in the register trought Javascript, with a specific sintax for the name, defining (trought Javascript) attributes and behavoirs...

Convention for inline glossary definitions?

Does anyone know if there is a convention for including inline definitions of words within HTML text?
I've made a documentation platform. It auto-generates glossaries, but I also want the user to have the option of having terms from the glossary definable inline, as the user reads, so they don't have to jump to the glossary page.
Possibilities:
transperambulation (?)
transperambulation [DEF]
transperambulation [def.]
transperambulation (nothing after the word, but the word itself underlined with dotted border)
It would need to be a hover (tooltip) effect as the word may also be a link, so clicking it is reserved for the link target.
Or is this a bad idea in general?
what about the abbr tag? it uses the title attr with a dotted underline http://www.w3schools.com/tags/tag_abbr.asp
i would use that

Can I use HTML tags inside an SVG tag?

I'd like to use regular HTML tags (for instance an input tag) within an SVG tag.
Why? I would like my SVG graphic to be able to get text from the user (e.g., the user clicks on a box drawn with SVG and enters text on it), so I was thinkig about using HTML input tags within an SVG tag. Is this possible?
If the answer is no (which most probably will), how can I allow a user edit SVG text?
There is already an answer to that question:
how to change svg text tag using javascript innerHTML
But its not accepted.
It seems to be possible when you look at this example
http://starkravingfinkle.org/blog/wp-content/uploads/2007/07/foreignobject-text.svg
from this source:
http://ajaxian.com/archives/foreignobject-hey-youve-got-html-in-my-svg

Is it ok to create anchors without href attributes?

If you take this example, <a name="xxx"></a> ... is this ok when creating an anchor?
I have always preferred to use an already created tag for my destinations.
If you are using this for in page navigation you can just just the id of the element rather than having to set up the anchor tag e.g.
link to stuff
<div id="stuff"></div>
I personally would not use an empty anchor tag.
For navigational purposes within one page, it's perfectly fine. Though that style of navigation is usually related to some kind of headings or titles, so usually most people end up surrounding the appropriate heading/title with the anchor. I guess it's better from a readability and maintenance point of view.
Of course, why not? You just create internal link to content block with this method.
Using an anchor tag without href is useless. It is simply put a text styling to the contents inside the tag.
But you can use a anchor tag without a href, But onthe onclcick event you can dynamically divert the navigation of page. We use simply in some sites to apply the style to the contents within the anchor tag.