On a website i am working on, when ever i select a radio-button, Google Chrome asks to translate the page from Norwegian, even though the page is written in English. It does this from time to time and I'm not sure why. i have tried to load the page in fire fox and Internet Explorer but i do not see this problem there. Does chrome have issues when using radio buttons, or could this be a problem in the code?
thanks for your time.
if you want so suppress google translate you can add the tag
<meta name="google" value="notranslate">
Or you can add the class notranslate to whichever item you don't want translated.
<span class="notranslate">
Related
I need to be able to translate my web application into another language. I enabled the google translate extension in chrome. When I load my company website with chrome the translate icon appears and I can translate the site. I then loaded my secure web application in chrome and the translate icon disappeared. My knowledge on how the translator works with web pages in minimal at best. Any help would be appreciated as I do not know where to begin. Any links to helpful articles on how the translator does its job would also be appreciated
I also had a problem with the google translate (gt) icon disappearing from the right side of the Chrome address bar. I believe I caused the problem myself as I was trying to come up with a way to use it to switch languages quickly using Keyboard Maestro.
I keep 2 Chrome windows open with 2 different gmail accounts, and the gt icon was only missing from one of the windows. I tried many things and couldn't get the gt icon to come back.
Eventually, I was able to fix the problem based on the procedure described on this page, which suggests going to this address: chrome://settings/languages to make sure the Offer to translate pages that aren't in a language you read option is on in the Languages section, as shown in this image:
In my case, the option was already set to on. So I turned it off, logged out of the account associated with that Chrome window, closed that browser window, and when I opened a fresh browser window for that gmail account the gt icon was back.
I'm using Chrome Version 96.0.4664.93 on a MacAir (M1, 2020) running MacOS 12.0.1
Is there a way to force Google Chrome to use the <title> tag data instead of writing the web page address?
Eg. <title> </title> is ignored by Chrome and the browser writes "[domain].com/index.html" on the tab instead of the expected space. The problem occurs whether I use an actual space or the HTML character code. Other major browsers correctly read the title data as a space.
So does anyone know if there are any other invisible characters that Chrome will actually "display"? I've tried a number of other &nb__; characters to no avail. I'm looking for an HTML solution if possible, because I access this site on a number of computers and I won't be able to install extensions in every situation.
And before I get any flack about having a blank title, this is a personal website I made for my own use, so I'm not worried about accessibility or other user's experience, just my own. I recently switched from Firefox to Chrome and this is really bugging me.
WebGL does not work in the following three scenarios:
(for the 'test webgl' site used get.webgl.org)
1 Start chrome, Google search for the 'test webgl' site, click on the link in the search result.
2 Go to the 'test webgl' site from a link in an email.
3 Start Chrome from a short cut or command prompt, "C:\Program Files\Google\Chrome\Application\chrome.exe" http://get.webgl.org/
This only happens when Chrome is not already running. In other words WebGL does not work when chrome starts up. However it does work if chrome is already running.
The best demonstration is scenario number 3, above. This starts chrome and goes to http://get.webgl.org/ and Webgl does not work. Then do exactly the same again but this time with chrome already open and Webgl works.
Would very much appreciate feedback or a solution, thanks.
Have also created various test sites in html, javascript and webgl, in order to find a work-around. For example if webgl is not available then allow the user to click on a link to open the page in a new tab, this does not work. However if the user opens a new tab then loads the page, webgl is detected and works.
In short, if a customer opens chrome and searches for your website (that has webgl content). Then clicks on the link, webgl will not work. It does not seem reasonable to then instruct the customer to open a new tab and then go to the same website a second time. So far have not been able to find a solution so that it just works without the customer having to fiddle around.
I realize that this may be a chrome issue as it does not occur in firefox, however am trying to find a javascript solution rather than waiting for chrome developers to fix it.
Thanks for any suggestions.
(Windows XP Pro, Chrome V36)
Hi Mack,
Thanks for your reply. The majority of visitors to my web site have XP and Chrome. I should imagine that this is true for quite a lot of peoples, websites.
Problem 1 The first fallback I had on my website was to detect if webgl is supported. If yes then continue as normal. If no then display a help page. This was simple and worked, however, google crawlers do not handle the javascript very well, therefore always index the webgl help page, rather than the home page.
Solution 1 Managed to fix this by having a popup box appear when webgl is not supported, giving the user a choice of whether to continue or go to the help page. The conditional code that processes the user response is arranged so that if the user is a google crawler then it simply 'falls through' and displays the html content of the home page, and not the help page.
There are lots of web sites that seem to have this same problem, including get.webgl.org, in other words, if you do a google search for a website, and that site contains webgl detection and fallback code, the search result always shows the fallback content, rather than the authors intended main content.
Problem 2 Now that I finally have the home page listed correctly by google, found that am still losing many customers, as they are starting chrome, searching google for my site 'suit yourself shirts', clicking the link in the result and being told incorrectly that webgl is not supported.
Am very interested in your solution but do not quite understand how it works. Have tried detection then page refresh or load the page in a new tab or display a link for the user to load the page, but none of these methods seem to work. Seems like quite a fundamental problem that would effect many webgl websites. Would be very greatfull if you could explain your suggestion a little further. Thanks for your help, kind regards - Gary
I am trying to open a pdf from my JQM webapp. I have tried iframes/embed/object, and none of those work on an iphone like they do on a desktop browser (scrolling, zooming, etc). I have settled with simply opening the pdf via a link Link. This works fine in the standard browser because the user can simply use the browser back button to navigate back to my app.
The issue that I am having, is that when a user saves the page to thier home screen and opens it using the chromeless safari browser, they no longer have the browser back button. I have tried adding target="_blank" to the link, but apparently JQM hijacks the link and prevents opening in a new page, and I have been unable to get the hacks to work.
I have also tried pdf.js, but I can't seem to even get that to work as my javascript knowledge is fairly limited, and the examples are pretty advanced. The only tutorial that I found used an old version which I couldn't get to work.
Are there any ways to bypass the JQM in openning a link in a new window (which would in turn open in the mobile safari rather than my chromeless web app), or are there any other suggestions for how to open a pdf from a webapp?
Just disable the default jQuery Mobile behaviour, by specifying data-ajax=false.
For example:
Link
See http://jquerymobile.com/demos/1.2.0/docs/pages/page-links.html
For my webApps I used https://docs.google.com/viewer to embed the pdf into my interface.
So, when I navigate the webApp by home screen icon, the app doesn't close when I open the pdf.
I met the same question: open pdf in webapp with html5.
I've tried several solutions: iframe、embed、pdf.js, but none of them is the best solution.
tips: iOS 9.x upper, open pdf with iframe only show the first page of the pdf file, and there will be a <img /> tag in the iframe body when you debug.
util now I still have this troublesome problem, anyone has solution please write your experience here.
Thank you.
Which editor adds this to the HTML files it creates? It is pretty obviously a Mac program.
<meta http-equiv="Content-Type" content="text/html;CHARSET=x-mac-roman">
I have a page that let's users upload an HTML file, and HtmlAgility chokes on this...
I'm just curious as to where this tag comes from, as I've never seen it..
Sam
It comes from BillGates' ripoff Word when it runs on MacOS and the user writes a Word document then chooses 'Save as WebPage'. The stupid thing is that the web page produced shows up beautifully in FireFox but Gates' own IE mucks up all the accents (I've been struggling with trying to iron out the problem for text written in French).