tel

Replacing tel or telprompt to call

ぃ、小莉子 提交于 2019-12-01 13:04:28
I've made an application is used to call predefined numbers upon button press. As far as i know the only way to make call inside app is to use "tel" or "telprompt". When i submitted an app i've received a rejection with this description: 2.5 Details Your app uses or references the following non-public APIs, which is a violation of the App Store Review Guidelines: teleprompt:// The use of non-public APIs is not permitted in the App Store because it can lead to a poor user experience should these APIs change. For my first submission I used "telprompt" to call, then I changed it to "tel" because

Replacing tel or telprompt to call

天大地大妈咪最大 提交于 2019-12-01 10:44:49
问题 I've made an application is used to call predefined numbers upon button press. As far as i know the only way to make call inside app is to use "tel" or "telprompt". When i submitted an app i've received a rejection with this description: 2.5 Details Your app uses or references the following non-public APIs, which is a violation of the App Store Review Guidelines: teleprompt:// The use of non-public APIs is not permitted in the App Store because it can lead to a poor user experience should

Rendering telephone links in HTL based on input from a Rich Text widget

故事扮演 提交于 2019-12-01 05:26:00
I have a component using the Rich Text Edit widget ( xtype="richtext" ) in my project that's used across the entire site as the default text component. The users would like to be able to insert phone links using the tel URI scheme into the text entered using this component. The dialog allows them to do so but when the contents of the Rich Text Edit are rendered in Sightly/HTL later on, the html context is used: {$text @ context='html'} Once this is done, the value of my attribute is ignored. The HTML stored in the repository is: <a href="tel:04242424242">Call us!</a> And what's actually

Rendering telephone links in HTL based on input from a Rich Text widget

旧巷老猫 提交于 2019-12-01 03:07:26
问题 I have a component using the Rich Text Edit widget ( xtype="richtext" ) in my project that's used across the entire site as the default text component. The users would like to be able to insert phone links using the tel URI scheme into the text entered using this component. The dialog allows them to do so but when the contents of the Rich Text Edit are rendered in Sightly/HTL later on, the html context is used: {$text @ context='html'} Once this is done, the value of my attribute is ignored.

How do I give option to dial an extension in Tel: link?

主宰稳场 提交于 2019-11-30 23:27:05
While putting a tel link as <a href="tel:+91123456789,,123">Dial</a> and clicking it from a mobile browser, only initial number gets transferred to dialer and not the commas or extension. I've tried p , w and ;ext= as well but nothing is working. p and w change to '7' and '9' respectively. Tested using Moto X 1st Gen. Ali Zia According to the documentation , the tel: scheme supports RFC 3966 . Reading these RFCs is a bit like reading cuneiform on clay tablets, but from what I can tell, your syntax is not part of that standard. It looks like you would want tel:+91123456789;ext=123 . UPDATE:

What's a reliable method for setting up telephone links for mobile browsers?

生来就可爱ヽ(ⅴ<●) 提交于 2019-11-30 17:16:21
I'm working on a quick page intended for mobile browsers. While there is little consistency between browsers on cell phones (the target audience), I have a phone number that I would like to be as easy as possible to dial from the users phone. A link seems the obvious choice; so I set up the following: <a href="tel:+18881235467">1-888-123-5467</a> This seems to work OK on more advanced browsers such as the Android & BlackBerry browsers, it's a lot less reliable on other phones. Any advice on making this link work consistently and or correctly will be greatly appreciated. FYI, this is a toll

iPhone Safari making a phone call

扶醉桌前 提交于 2019-11-30 07:27:27
问题 Is there something I can put in the code for an HTML page I am making for Safari on iPhone to make a call when clicked on? Something similar to: <a href="tel://1300111222">click to call</a> 回答1: Try to remove // from your link, that is <a href="tel:1300111222">click to call</a> 回答2: As Nava answered, remove // from your link. But if you are using same web-application for desktop as well as mobile, then this won't work for your desktop and when you click on link, page will gone to "tel

Detecting HTML <a> click-to-call support in Javascript

爷,独闯天下 提交于 2019-11-30 06:38:28
问题 There are two ways to have click-to-call links in HTML <a href="wtai://wp/mc;+1800229933</a> WTAI style (Nokia, others) <a href="tel:+1-800-275-2273">Call Apple Customer Support at 1-800-275-2273</a>. TEL style (Apple) How one can detect which format is supported by current user agent in Javascript? Is it possible to do the detection without relying the user agent string More info http://www.mobilexweb.com/blog/click-to-call-links-mobile-browsers http://www.raizlabs.com/blog/2007/07/02/iphone

Dealing with tel: anchor

一笑奈何 提交于 2019-11-30 05:42:38
问题 I have an anchor to a telephone number. On phones is great. On desktops with Skype or Google Voice it's good. The problem is on desktops that just don't know how to deal with that. What should I do? Detect if it's not mobile and change the link? I still want the link to show, just the URL to be different. Is there a better way? If not, how do I detect mobile in JavaScript in order to change the href attribute? Thank you. 回答1: To detect if the browser is launching from a mobile in JavaScript:

What's a reliable method for setting up telephone links for mobile browsers?

蓝咒 提交于 2019-11-30 00:42:37
问题 I'm working on a quick page intended for mobile browsers. While there is little consistency between browsers on cell phones (the target audience), I have a phone number that I would like to be as easy as possible to dial from the users phone. A link seems the obvious choice; so I set up the following: <a href="tel:+18881235467">1-888-123-5467</a> This seems to work OK on more advanced browsers such as the Android & BlackBerry browsers, it's a lot less reliable on other phones. Any advice on