|
substitute posted:Probably just a number on screen that contains a dash. When I am working with product numbers like that, I just preemptively style those specific areas so that once iOS automatically creates the inappropriate links they look like regular text, and then unwrap them with jQuery once the page fully loads. Your way seems backwards!
|
#
¿
Oct 16, 2014 14:32
|
|
|
|
| # ¿ May 16, 2024 03:00 |
|
|
For numbers that iOS thinks are phone numbers but aren't: - I add the style so that it looks like regular text as soon as it renders, and continues to, if you're a crazy person who turned off Javascript on their phone's browser. - I use jQuery to strip the unwanted a[href|="tel:"] links out as soon as any more important Javascript is done. (Practically, this happens almost instantly, but the style prevents any weird flashes of link styling if it doesn't happen quickly enough.) Actual phone numbers elsewhere on the site still get automatically created on iOS (and Android, I think), so I don't have to worry about adding tel: links manually and suppressing them on desktop browsers.
|
|
#
¿
Oct 16, 2014 20:46
|
|
|
substitute posted:Got it, thanks for clarifying. So iOS adds the <a href="tel:..> to the source at output? Yeah, the phone OSes make them clickable by default. It would be great if we could just put them all there all the time, but desktop browsers don't handle tel: links very well.
|
|
#
¿
Oct 17, 2014 15:44
|
|
|
NovemberMike posted:I didn't really notice it. Same. You could ditch the separate category pages and just do filtering on click with this fancier version of Masonry: http://isotope.metafizzy.co
|
|
#
¿
Mar 1, 2015 00:30
|
|
|
I'm not really sure where to post this question, so, here goes: The hosted CMS my agency uses is not HIPPA-compliant, and since switching to a different one is out of the question for the short term, the solution I've come up with for clients that require HIPPA compliance is: - implement on our CMS as usual - create a flat HTML version of the site using wget on the temp URL recursively - use find and replace to remove <script> tags that are no longer needed and causes console errors - upload the flat HTML version to a HIPPA-compliant host Obviously, this makes updates a bit labor-intensive, and I'd like to automate this whole process so that it occurs automatically. My initial thought was Node since I'm already comfortable with Javascript, but I can't really find any modules that replicate this particular use case of wget. Anyone ever had to do anything similar to this? I'm a front-end dev who is way out of his comfort zone, so alternative ideas are absolutely welcome.
|
|
#
¿
May 27, 2015 22:45
|
|