Member Avatar for unikorndesigns

Guys,
I am facing a major issue with my html template. On my PC the links are working fine but when i viewed the website on my mobile, the links are not working at all. Here is the

Thanks in advance.

  • 6 Contributors
  • 10 Replies
  • 216 Views
  • 5 Days Discussion Span
  • Latest Post Latest Post by Eng. Hadi

Dani AI

Generated

Summary of the thread: sees links work on desktop but some "read more" buttons fail on an Android S3 while and report iOS is fine and reports the navigation works but some read-more links do not. That pattern most often points to a client-side interaction problem (CSS overlay, non-semantic clickable markup, or a JS event that doesn’t fire on that Android browser) rather than a broken remote URL.

Quick checklist of likely causes to verify (based on the reports from this thread and the earlier suggestions by and ):

  • Interactive elements implemented as non-anchor elements with only onclick handlers: some mobile browsers need semantic anchors or explicit touch handlers for reliable taps.
  • An invisible overlay or fixed element with higher z-index/pointer-events intercepting taps.
  • A JavaScript error that prevents later handlers from running (check the console on the device).
  • Use of placeholder hrefs or prevention logic that accidentally stops normal navigation on some WebViews.

Example of a robust, progressive approach (use real anchors + delegated JS only for enhancement):

document.addEventListener('click', function (e) {
  var a = e.target.closest && e.target.closest('a.read-more');
  if (!a) return;
  var href = a.getAttribute('href') || '';
  if (href.charAt(0) === '#') {
    e.preventDefault();
    var target = document.getElementById(href.slice(1));
    if (target) target.scrollIntoView({ behavior: 'smooth' });
  }
}, false);

Practical debugging notes: use remote inspection from desktop Chrome to watch console output and event listeners on the Android device, temporarily disable JavaScript to verify native anchor fallback, test in multiple Android browsers to isolate WebView quirks, and inspect computed styles for overlapping elements or CSS pointer-events. Converting clickable markup to semantic anchors (or adding role/tabindex) and using delegated handlers that work with both touch and click resolves similar cross-device differences.

Recommended Answers

All 10 Replies

Member Avatar for JorgeM

I just tried from an iOS device and the navigation and read more links appear to be working.

Member Avatar for unikorndesigns

hmm...its weird cuz its not working in my android phone. I'm an S3

Member Avatar for Member #671080

The navigation links work fine on my S3 but the read more links seem to do nothing.

Edit. The Finance & Accounting Outsourcing 'read more' link does work, the other read more links don't work on my S3

Edited by Member #671080
Member Avatar for annaharris

I checked this link in my iPhone; it's working fine.

Member Avatar for unikorndesigns

Any solution to that link problem. I checked it in IE9, the navigation links are ok but the read more buttons are doing nothing.

Member Avatar for BMXDad

Are they supposed to be defaulting to a hash tag(#)s

Member Avatar for unikorndesigns

nope...its linked to another id of the same page and onclick it would scroll to that section with the appropriate id..

Member Avatar for BMXDad

This is what I get for a link, no page or anchor ... is this static or dynamic content?

Member Avatar for unikorndesigns 
its static....instead of an anchor link, i assigned an event to the buttons so onclick it goes to the page i want. could you guys check it out from your end? In your smartphones! Thanks
Member Avatar for Eng. Hadi

Did you put the protocol in front of the url in your html code? if not please put it so your link will be ,some older mobile browsers are not "tolerant".

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.