Standardize TARGIT URLs with Embedded Links
The way TARGIT currently builds out embedded links (using 2 hash-signs) is an incorrect URL. The information that appears after the first hash symbol is a fragment identifier, which can only be interpreted by the local web browser and not passed to the remote web server. The second hash sign breaks the URL, as a fragment cannot have a '#' in it.
My company and I have been trying to embed TARGIT dashboards in our mobile CRM platform, but the broken URL is preventing us from accomplishing this. I would imagine that other companies are facing this dilemma, and think that TARGIT should standardize URLs to be compatible across all browsers, in accordance with common web practice.
Comments
3 comments