Sorry, with webkit, this might do the trick:
Joseph R. B. Taylor
Web Designer/Developer
--
Sites by Joe, LLC
"Clean, Simple and Elegant Web Design
Web: http://sitesbyjoe.c
I think what he means is is there any way to avoid the product code being
regarded as phone number rather than a product code.
On Fri, Jan 28, 2011 at 8:54 AM, Joseph Taylor wrote:
> You can wrap the phone numbers in an anchor tag:
>
> 1234567890
>
> The "tel:" is sorta like the "mailto:"; in
You can wrap the phone numbers in an anchor tag:
1234567890
The "tel:" is sorta like the "mailto:" in a link but for phones.
Joseph R. B. Taylor
Web Designer/Developer
--
Sites by Joe,
I am currently out of the office until Monday the 31st of January. For
any urgent issues please contact my Team Leader Luis Landaverde or
alternatively I will respond to your emal on my return.
--
*Ryan Blunden*
Web Specialists Tech Lead
*Mavericks Online - Web Solutions*
Flight Centre Limited
Title: Nagem
We're doing a mobile project for our e-commerce. Some issue I've a
product code (676767 e.g.) and the markup understand that's a phone
number. How can I fix this?
Cheers.
--
Leonardo
On 1/27/11 6:42 AM, Steve Green wrote:
That's exactly my point. At any point in time there will be projects
where you should use safe, well-understood, well-supported
technologies and there will be other projects where you can try out
new cutting-edge ones. When making this choice, you should put
I found this link interesting within the context of the current discussion.
"
HTML: The standard that failed?
HTML is officially whatever the top browser vendors say it is at the moment.
You call that a standard?
"
http://www.infoworld.com/d/developer-world/html-the-standard-failed-585
Christie
That's exactly my point. At any point in time there will be projects
where you should use safe, well-understood, well-supported technologies
and there will be other projects where you can try out new cutting-edge
ones. When making this choice, you should put aside your personal
preferences and broa
I think it's all a matter of careful implementation. All such new things
must be used in agreement with client. Using graceful degradation, knowing
which browsers to support, what technologies available, etc. If we will not
use this new technics now, then it wil be hard for browser vendors, web
ser
Both those examples are interesting, and underpin my hesitation to move
to HTML5.
In 2004 one of the largest London design agencies persuaded a corporate
client that they could build a complex website using pure CSS layout. We
did the compatibility testing (Netscape 6, IE6, Opera 6 etc) and it wa
I hear what you are saying Steve, but isn't that always the case?
The HTML5 scenario is becoming de rigueur now, just as a) tables vs divs and
floats and b)XHTML were years ago. It's only by becoming familiar with
'changes' that one can decide for oneself if there are advantages (or not).
It'
In my view it depends on who you are and who is paying for the website
development. If you are building a website for yourself, by all means
spend as much time as you like learning about the new technologies and
implementing them.
However, if you are building a website for someone else, you shoul
12 matches
Mail list logo
