phone-tag | Server-side repo for mobile , geolocation-based game of tag | Frontend Framework library

by RebootJeff JavaScript Version: Current License: No License

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | phone-tag Summary

phone-tag is a JavaScript library typically used in User Interface, Frontend Framework, React applications. phone-tag has no bugs, it has no vulnerabilities and it has low support. You can download it from GitHub.

Phone Tag (working title) - Server.

Support

Quality

Security

License

Reuse

Support

phone-tag has a low active ecosystem.

It has 25 star(s) with 4 fork(s). There are 3 watchers for this library.

It had no major release in the last 6 months.

phone-tag has no issues reported. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of phone-tag is current.

Quality

phone-tag has no bugs reported.

Security

phone-tag has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

phone-tag does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

phone-tag releases are not available. You will need to build from source code and install.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of phone-tag

Get all kandi verified functions for this library.

phone-tag Key Features

No Key Features are available at this moment for phone-tag.

phone-tag Examples and Code Snippets

No Code Snippets are available at this moment for phone-tag.

Community Discussions

Trending Discussions on phone-tag

javascript regex doesn't match emails when url matching is passed

'tel' attribute not working in href of anchor tag in rich text editor in classic UI in AEM 6.1

QUESTION

javascript regex doesn't match emails when url matching is passed

Asked 2019-Apr-21 at 15:10

Am trying to match email,phone,email,hashtags and mention tag in a message and insert them inside a hyper link. But am having problem with my regex as it doesn't match emails as mail instead it match as a link.

Below is a working example.

...

ANSWER

Answered 2019-Apr-21 at 15:10

I think the problem is that search for the "chat-message-link" is "eating" the domain in the email-address. I don't know if that's generally applicable, but I changed the search so that if would start at the beginning of the line...

Source https://stackoverflow.com/questions/55783246

QUESTION

'tel' attribute not working in href of anchor tag in rich text editor in classic UI in AEM 6.1

Asked 2017-Aug-02 at 08:44

I am using AEM 6.1 SP2 , I am trying to enable 'tel' attribute in the href of anchor tag to make the click to call functionality work. I have already added 'htmlRules' node and links node under htmlRules node with 'protocols' property as [http://, https://, ftp://, tel:, mailto:, file://]

as specified in the link - http://labs.6dglobal.com/blog/2013-01-11/configuring-telephone-tags-within-rich-text-components-and-link-checker/

The 'validateHref' function in rte.js does read the 'protocols' property and validates the 'tel ' attribute as valid, but not sure why the 'tel' attribute does not persist in the markup when 'ok' is clicked in the author dialog.

this is the anchor tag -

1234 567 89

and this is how it renders as markup on page -

...

ANSWER

Answered 2017-Aug-01 at 07:20

It seems that the solution you linked in the question is not applicable for the latest versions of AEM.

The mechanism that is now responsible for removing href starting with tel is HTL XSS protection that scans properties before being written. The simplest way to avoid that is disabling it in your Rich Text component: ${properties.text @ context='unsafe'}. That is not the safest solution though and instead it is better to extend XSS protection configuration with these steps:

Overlay XSS configuration files by copying it from libs to apps:

/libs/cq/xssprotection/config.xml -> /apps/cq/xssprotection/config.xml /libs/sling/xss/config.xml -> /apps/sling/xss/config.xml

Add protocol with new regexp for tel:

Add telURL to regexp-list of anchor href attribute:

It might be also required to restart AEM instance after doing these changes.

In the case of issues, you can read more about it on this blog page and this Stackoverflow post.

Additionally, Link Checker mechanism may still mark your link as invalid on edit mode, and on publish it can be removed.

Depending if you need it to make it work to one or all specific anchors or all anchors in your app, you can either:

add x-cq-linkchecker="skip" attribute to your anchor, as i.net suggested in the comment under your post
or if you would like to allow adding tel to any possible anchor on the page, add exception tel: Special Link Prefixes in Day CQ Link Checker Service OSGI service. Please note that then the service configuration needs to be applied on all author and publish instances.

Source https://stackoverflow.com/questions/45371683

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install phone-tag

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: