Chrome bug?

The band site which I have built with Muse works fine with Firefox, Safari, and Opera but in Chrome my button to to the Homepage stops working after I press any of the other menu buttons in the list. I'm baffled, can anyone figure out what's going on? Site is ekpb.org.uk.

Hello Rob,
This looks like some content is overlapping the Home button on the other pages. You may be using the same master page on all the pages (that can be seen in the menu). If that is true, then the issue is probably with that master page. Can you go to the master page that is applied to the pages and select all to see if some content (like an empty text box, rectangle) or the frame of any of the contents in that page is overlapping the home button?
Although if the above is true, then it should've behaved the same on all the browsers, but it's still worth a try.
Hope this helps.
Cheers
Parikshit

Similar Messages

Is chroma bug solved in new version of AME5.5 when transcoding to ProRes?

About a year ago I had posted to the forums about a "chroma bug" observed by me and others when using Adobe Media Encoder v.5.0.1 to transcode AVCHD to Pros Res 422. It would result in chroma bleed and a softer image versus a sharper transcode using Apple's Compressor. I have attached a link here to my previous posting which shows jpeg images of what AME v.5.0.1 was doing to the image.
Adobe Forums: For Adobe Premiere users encoding to...
I would download a trial version of the new Adobe Media Encoder 5.5 (but I believe because it's a trial version that they disable transcoding from AVCHD feature).
Are there any current users of AME 5.5 out there encoding to Pro Res? If so, what have been your results?
My hope is that this chroma bug issue is solved for v.5.5 but I really have no definitive way to test it unless I purchase the upgrade...as the trial version won't allow me to transcode from AVCHD.
The catch 22 is that I didn't want to purchase the upgrade until I knew the bug was fixed. I reported it to Adobe at the time of my initial posting but received no feedback or acknowledgement of the issue. Most of my editing is done in Pro Res rather than natively...hence this is an important item for me.
Thanks for any thoughts other users can share.
John

as the trial version won't allow me to transcode from AVCHD.
Sure it will. The CS5.5 trial now has all MPEG limitations removed, so you can fully work with all supported formats for 30 days in the trial.
I seem to recall reading something about the chroma sampling bug being fixed, or at least, improved. But give the trial a shot and you'll know for sure.

Chroma Upsampling Error (Chroma Bug) on new iMac

I just scored my 24" 2.4GHz iMac last Friday, and I've been geekin' on it non-stop ever since. I'm completely in love with it. I do have one complaint tho, and it goes to the DVD drive and it's MPEG decoder: my 24" iMac displays a glaringly obvious chroma bug problem on animated DVD content ("The Inredibles", and "The Lion King" are prime examples). I'm guessing this is only "glaringly obvious" because the screen is sharper and clearer than any I've used before :-/
If you're not familiar with this problem, the short version is that on high definition progressive displays, the color information in incorrectly decoded MPEG-2 content (the format for DVD, among other uses) appears blocky and jagged -particularly in bright red objects. You may have a screen full of crystal clear detail, but everything red looks like it has been worked over with a hot bag of nickles. The problem is endemic to the entire chroma (color) portion of the signal, but most obvious in bright red areas.
The chroma upsampling conversion problem has been understood and solutions for it have been identified for years. Why is Apple still using MPEG decoder manufacturers who can't keep up with their delisciously-sharp HD displays? Nobody (that I know of) is using the dual-layer superdrive in any kind of interlaced NTSC environment. In other words, there's no excuse for this.
I'm guessing that within a year or two, they'll be stufing BlueRay or HD DVD drives in these boxes by default, and I'll be willing to bet they won't bother to address it then either, because the content will be of higher resolution, and therefore less noticable. It just ticks me off that they would leave such a huge compromise in the DVD playback capability of these new machines.
Anyone else notice it?

I noticed the effect. Cars is a grievous example, but it's apparent on non-animated DVDs as well. It does seem to be noticeable only on bright reds. (Just about unwatchable, however, was an old movie "Track of the Cat" - if you've seen it, you'll guess why.)
Could you explain a bit more about the cause of this, as you understand it? Why would it be specific to the new iMac? What can be done to alleviate/correct?

How to fix panelCollection toolbar buttons layout in Chrome [BUG]

Hello,
The bug is here for years.
I've got a panelCollection with a toolbar and a number of toolbar buttons in it.
In IE/Firefox it's all fine.
In Google Chrome some buttons get randomly hidden after PPRs. One can only tab to them.
Take a look at the screenshot: http://img252.imageshack.us/img252/6218/adftoolbarchrome.png
Here's page code:<af:panelCollection id="pc_tree" featuresOff="statusBar" defaultToolbarItemDisplay="icon">
                <f:facet name="menus"/>
                <f:facet name="toolbar">
                  <af:toolbar id="t9" partialTriggers="::pc1:t1 tree1">
                    <af:commandToolbarButton text="#{templateBundle.EXPAND}" id="ctb_expand"
                                             actionListener="#{backingBeanScope.TemplateBean1.expandTemplateTree}"
                                             icon="/img/tree.png"
                                             disabled="#{bindings.TemplateView1Iterator.currentRow == null}"/>
                    <af:spacer width="10" height="10" id="s1"/>
                    <af:commandToolbarButton text="Создать компоненту" id="ctb_del"
                                             disabled="#{bindings.TemplateView1Iterator.currentRow == null}"
                                             icon="/img/tree_1_level_create.png"
                                             disabledIcon="/img/tree_1_level_create_bw.png" accessKey="1">
                      <af:showPopupBehavior popupId="::p2_create"/>
                    </af:commandToolbarButton>
                    <af:commandToolbarButton text="Создать параметр" id="ctb3" icon="/img/tree_2_level_create.png"
                                             disabled="#{bindings.ComponentView1Iterator.currentRow == null || bindings.ComponentIdkComponent.inputValue == '3' || bindings.ComponentIdkComponent.inputValue == '4'}"
                                             disabledIcon="/img/tree_2_level_create_bw.png" accessKey="2">
                      <af:showPopupBehavior popupId="::p3_create"/>
                    </af:commandToolbarButton>
                    <af:commandToolbarButton text="Создать показатель" id="ctb4"
                                             disabled="#{bindings.ComponentView1Iterator.currentRow == null || bindings.ComponentIdkComponent.inputValue != '2'}"
                                             icon="/img/tree_3_level_create.png"
                                             disabledIcon="/img/tree_3_level_create_bw.png" accessKey="3">
                      <af:showPopupBehavior popupId="::p2" alignId="ctb4"/>
                    </af:commandToolbarButton>
                    <af:commandToolbarButton shortDesc="Редактировать" id="ctb_edit" icon="/img/edit.png"
                                             disabled="#{bindings.ComponentAllView1Iterator.currentRow == null}"
                                             accessKey="e">
                      <af:showPopupBehavior popupId="#{bindings.ComponentIdkComponent.inputValue == '1' ? '::p2_edit' : (bindings.ComponentIdkComponent.inputValue == '2' ? '::p3_edit' : '::p4_edit')}"/>
                    </af:commandToolbarButton>
                    <af:commandToolbarButton id="ctb23" icon="/img/delete.png"
                                             shortDesc="#{templateBundle.COMPONENT_DELETE}"
                                             disabledIcon="/img/delete_bw.png"
                                             disabled="#{bindings.ComponentView1Iterator.currentRow == null || bindings.ComponentIsDelete.inputValue != '1'}">
                      <af:showPopupBehavior popupId="::p_del"/>
                    </af:commandToolbarButton>
                    
                    <af:spacer width="10" height="10" id="s2"/>
                  </af:toolbar>
                </f:facet>
</af:panelCollection>

Tried once.
About a year ago. Got an answer like "Google should fix their bugs themselves".
Should try another one time.
Is there any workaround? I can't be the only person with this problem.
Here is a testcase application: http://dl.dropbox.com/u/8422244/ADF/ToolbarButtonsApp.zip
In Google Chrome right-hand toolbar buttons get hidden after table row selection or left links click (on PPR).
Found the answer at once. ADF conflicts with Chrome AdBlock extension.

PDF plug-in for Chrome bug

I am experiencing a very odd problem. Whenever I try to convert a web page into a PDF on a site where I had to log in (e.g. Amazon), my resulting PDF file contains my log in page, NOT the actual page I tried to convert.

Yes, it's an identical copy (incl. version, dates and digitally-signed certs) as far as I can see on all these 3 folders located at C:\Program files\
-> Adobe\Reader 9.0\Reader\Browser -> nppdf32.dll
-> Mozilla Firefox\plugins -> nppdf32.dll
-> Internet Explorer\PLUGINS -> nppdf32.dll <--- This folder and file
Please also note that IE Activex controls (3 files - also at version 9.5.2.295) are located at C:\Program files\Common files\Adobe\Acrobat\ActiveX\
-> AcroPDF.dll (PDF Browser Control)
-> AcroIEHelper.dll (Adobe PDF Helper for Internet Explorer) and
-> AcroIEHelperShim.dll
Weird indeed! Any ideas?

Google Chrome messed up UI text

So, after installing Google Chrome from the AUR, I noticed first thing that the UI text was obfuscated. this includes both the text in tab labels, the location bar, and other UI elements, but not the text of web pages.
Here's a scrot: http://i.imgur.com/05eMBXA.png
I don't really have any starting points on this, so I appreciate any help I could get.

Don't need to create test case, someone else has already reported it on Chrome bug list.
If this is a problem to you (and I think it will be if you have an applet with menus that is used on Chrome) perhaps you could follow this link,
and star the item. (I note that this also stops drop lists from working.)
To star the item, from the page, click 'back to list', find item 937, and click on the favourite star.
http://code.google.com/p/chromium/issues/detail?id=937&q=java&colspec=ID%20Stars%20Pri%20Area%20Type%20Status%20Summary%20Modified%20Owner

Google Chrome pop-up windows problems in Oracle BPM Workspace

Hi to everyone!
I posted this thread in other location and nobody helps me.
I think this location is the best. See the followin content please and help me!
https://forums.oracle.com/thread/2529006?tstart=0
Regards.

Don't need to create test case, someone else has already reported it on Chrome bug list.
If this is a problem to you (and I think it will be if you have an applet with menus that is used on Chrome) perhaps you could follow this link,
and star the item. (I note that this also stops drop lists from working.)
To star the item, from the page, click 'back to list', find item 937, and click on the favourite star.
http://code.google.com/p/chromium/issues/detail?id=937&q=java&colspec=ID%20Stars%20Pri%20Area%20Type%20Status%20Summary%20Modified%20Owner

Rendering of HomeHub page on Chrome

I have an oddity on the rendering of the HomeHub page on Chrome (26.0.1410.43 m, also on Version 26.0.1410.64 m).
This seems to be a Chrome bug not HomeHub. Has anyone else seen similar?
The menus are almost unreadable. The reason is that Chrome cannot load the background colour images http://192.168.1.254/images/adv_nav_top.gif or http://192.168.1.254/images/adv_nav_mid.gif when called from the HomeHub pages. They load standalone without problems, just not in their proper context.
Not too much of a worry, I can just make them out and know where most are anyway, or I can use another browser; just odd.
Solved!
Go to Solution.

Really odd. OK for me on Firefox 19.0.2. Also on 20.0.
But thanks for the hint that put me on the right track: ---->>>
~~~
SOLVED (for me at least). It is the Avast ad-blocker that is causing the problem.
It must have decided that 'adv' in the image name indicated advert?
Put in the HomeHub as an exception.

Installing Flash Player with new Google Chrome

hello, i need help. i decided to try out the new google
chrome and it works really well, but the flash player is not
updated...so i've been trying to do so but its either my computer
won't let me or somethings wrong.
i can put the "install flash drive" thing or button on my
desktop..i press it. it asks to run it and i do. it looks like its
installing but then it completes and just says close. i press close
and nothing happens... i go back to say youtube and it didn't work.
whats going on? can you help me?

Technically since it's still in beta it's unsupported.
However, if you have a previous Flash Player PLUGIN install on your
system, then installing Chrome should just pick up that plugin.
So if you had Firefox already, with the Flash Player 10
plugin working, you wouldn't need to do anything.
But if you only had IE with Flash, then you only have the
Flash Player ACtiveX control, not the plugin. And chrome won't work
with that. At that point if you have install issues with the plugin
you should actually contact Google (because it's beta..) if they
have Flash Player issues they'll work with us directly to address
them for their final release.
Now, if SOME sites work, like youtube, then you do NOT have a
Flash Player install problems. Rather, sites that do not work have
a Flash Player DETECTION problem, and you should inform them of
this as well.
You can file chrome bugs here:
http://googlechromereleases.blogspot.com/
That all said, I have seen some chrome Flash Player
workarounds out there, though they use a somewhat extra-legal
download of the player. So I won't mention them here. But I'm sure
you could find them if you need one..

Clicking Lync meeting URL in Chrome does not open Lync

We have some staff that use Chrome as their default browser.
In OWA, if they click on a URL to join a Lync meeting, and the Lync 2013 App is installed on their computer, the App does not open. Instead a Lync Web App opens.
Is this happening because of a shortcoming in Lync or in Chrome?
We'd prefer not to set IE as the default browser and not to install the IE Tab chrome plugin - I guess I'd like to understand a bit more about why the full App isn't called?

There is a chance that this issue is caused by Lync using a deprecated model in the plugin. Honestly, I don't even understand the second half of the previous sentence, but a similar issue in Chrome for Mac was traced to that root cause. Quoting
from a Chromium developer:
#12 [email protected]
Okay, thanks; that's what I needed.
The reason this started with Chrome 22 is that we dropped support for legacy graphics and event models (QuickDraw and Carbon, respectively) that have been deprecated for several years. To remain compatible with Mac Chrome 22+, plugins need to negotiate the new CoreGraphics and Cocoa models. Almost all the popular plugins have updated over the last several years, and I had reached out to the vendors of plugins I was aware to let them know. I hadn't heard of this plugin, so I hadn't contacted them.
The fix here is for them to release an updated version of their plugin. If their plugin doesn't draw or handle events (and it sounds like it doesn't, but is just a bridge to the app) then adding the negotiation to the plugin is a trivial change in their plugin.
I don't see any contact info for them, so what would help is for anyone experiencing this to contact Microsoft Lync technical support or any other contact point you have to let them know that their plugin needs to be updated, and point them to this bug for details. Feel free to provide them my email address in case they want to follow up in any way.
With a view to getting help from the Microsoft Lync team to investigate this, I've opened a call with Office 365 support. Initially, first line support could not get permission to install Chrome and replicate the bug, and thus wanted to close the call
as it potentially related to non-microsoft software. I've asked for the call to be escalated to a more senior tier that would have permission to install Chrome and hopefully someone somewhere is working on it.
Can I ask that anyone experiencing the same issue please raises a call with Office 365 about this, as a flurry of similar calls at the same time will get someone's attention - as all of us that work on helpdesks know too well!
Thanks to the 12 people that have starred the issue on the Chrome bug tracker in the last week.

Possible legal case issue with google chrome pepper flash player.

Ok so i have been on the phone to adobe for about an hour and this is the result.
As far as adobe are concerned their flash player works fine which it does.
However the google chrome Pepper flash player is obviously broken.
Now adobe say this has nothing to do with them their flash player is fine and googles version of adobe flash player has nothing to do with ADOBE either.
So why when you go into chrome plugin settings it says ADOBE flash player.
It doesn't say Google Flash player.
It says ADOBE Flash player.
So it seem to me that either google have stolen the Adobe flash player then made their own and broke it. OR Adobe let them make their own version and is fully aware of the issue but doesn't care?
How can Adobe ignore this issue for so long is disgraceful.
Adobe should be in contact with google saying what have you done to OUR Flash player.
Please the CEO of adobe should sort this out OR at least provide evidence that google hasn't stole Adobe flash player and broke it.
This situation is completely unacceptable and i belive a legal case should be opened if Adobe has NOT given permission for google to use and implement a version of ADOBE's Flash player.

your not going to like this, but i would of said the exact same thing myself, im a flash developer, i use chrome as my main browser with pepper running for general use. and from day to day im looking at javascript websites with simple little flash video players and adverts with spinning bitmaps, with no issues apart from the usual crashes when running flash videos, followed by that "oh snap" error message, which im sure the 18 year olds developing chrome find very ammusing. And of course when im developing flash applications im using the debugger version of the flash player in all my browsers like you should do, then i come to test my app on a pepper enabled instance of chrome one day and oh look at that nothing works. maybe if your running some basic timeline animation of a spinning dollar sign or a youtube video with some kids jumping off a roof it works, but a hell of alot is broken, loaders, loading fonts, uploading files, reloading cached files, and a plethora of things iv read in forums that i cant even get to try because i cant get anything to load consistently or find a debugger version of the pepper player to do a getStackTrace. i tried emptying all the caches and data from hosted apps, i tried deleting preference folders, tried recreating flash projects in flash builder from scratch, tried different versions of windows, tried testing it in the chrome beta, but that's even worse because instead of posting an error message it just hangs on a black screen in my app. none of this happens in any other version of the flash player i have tested so far, im tracking all errors that users of my app run into by logging them to a database and all of them are specific to pepper, and reproducable. In chromes bug reporting section there's a long list of these kinds of issues, its been like this for months, peoples businesses are being ruined by this stupid tiny little .dll file and the only solution anyone has found, other than the odd hack that fixes some bugs like setting video resolution to 479 instead of 480 to make a video stream play because google didnt bother to test anything other then the most basic default functions... Is to just throw a warning message to people with pepper player to go into their chrome plugins page, press a tiny little button in the corner to show some complicated dll file information, press another tiny disable button under the not very well marked pepflashplayer.dll, and then select always allow at the bottom so you don't have to deal with chrome blocking any working flash player other than pepper from running because its out of date. which in the end probably takes longer than installing the real flash player in the first place, there is literally no need for this damn dll file to even exist and for some mind blowing reason it has the exact same version number as every other flash player i have tried, which all work flawlessly. and also then obviously most people ignore the warning messages, continue to use your app wonder why its crashing, get frustrated and leave... So my only alternative so far is to totally block anyone using pepper player from even being able to load my app and tell them to do all of the above or use Internet explorer which seems to actually have a working built in flash player. so that instantly cuts out, as ofFebruary 2013, 50.0 % of Internet users unless they boot up internet explorer then manually navigate back to my webpage. which can make a huge dent to the amount of people who actually bother to even try your app.
Now you may be saying to yourself "well he sounds a bit miffed about this pepper player that for me seems to work fine". maybe there's some kind of hack way to get swfs running in pepper that only some of you in the know, know about, google doesn't have any answers, when i rang adobe they were utterly clueless, when i rang google there wasn't even a human being to talk to from that faceless corporate monstrosity. and iv got 4 years worth of development time riding on this damn flash app which, unless adobe pull the plug on pepper, or google learn how to bundle other peoples software. is totally useless just as im trying to deploy it, and im going to have to copy and paste the whole lot into some .js files and try to reverse engineer it all into javascript which means gutting all the stuff that you can only do in flash, which is about half of it. now obviously you start asking questions like, how could it be possible that a version of flash this flea-ridden was ever allowed to be let out into the jungle when sooooo much is at risk for certain types of businesses that rely on this technology. you could literally put people out of a job by doing this, the man on the phone from adobe says well its not our problem its googles version and they are in charge of it, well if that's the case you better pull the licensing quick fast because it makes adobe look bad and the the flash brand look even worse. normal chrome users who arn't even trying to peddle their wares made in flash are even complaining that its "poisoning" their beloved chromium, and the most they have to suffer with is a buggy experience in a flash game but those of us with serious time and work invested into flash and businesses based on it are utterly fuming.
Now, either you think this is all nonsense, you see no evidence, i must be doing something wrong, and all these cases im reading are just my imagination. Or you are fully aware of this situation and you are just saying the thing devs including myself always have to say to our users when we don't have a good answer or time to worry about it "Everything works great on my system, just submit a bug report". or you are so disconnected that you simply don't know about it yet and this is just a total waste of my time and anybody worth talking to his hidden deep in the bowels of adobe barred from communicating with the outside world.
What i want to hear is that indeed you are fully aware of and informed about these issues, and within 1 month the pepper player will be removed from chrome and users will be allowed to use the official flash player from adobe which will remain stable and fully functional.

[SOLVED] Google chrome/chromium freezing when typing in address bar

Hello again everyone, sorry to bother you.
Im using Arch 64 bit + kde.
Recently my chromium began freezing at random when I begin typing in the address bar. Since it persisted after several updates I installed google chrome beta from AUR, and the problem persists there. I've tried deleting the configuration directory to no avail.
I am a web developer and therefore this is kind of extremely annoying, I need more browsers than just Firefox so I thought about asking your help, are there any of you with a 64 bit arch system in which chrome works flawlessly? Did you do anything special?
Im beggining to think this is a chrome bug:
http://www.google.com/support/forum/p/C … 253b&hl=en
I found as well an old thread here in the forums:
https://bbs.archlinux.org/viewtopic.php?id=129632
But I decided to not be a thread necromancer.
My google chrome version is: 18.0.1025.39 beta
My chromium version is: 17.0.963.56
I'm willing to recompile this thing if you think that will help, but I've heard horrible stories about compiling chrome. Any help will be tremendously appreciated.
Last edited by denn1s (2012-03-10 17:46:50)

yes, my card is nvidia 8600GT.
This morning I spent a few experiments.
1. I noticed that if you run full-screen application (game), then when you try to switch to the console - is a black screen without text, a problem arises as in KDE and in xfce, if you switch to the console without running full screen applications, the when switching to the console you can see the shell prompt to login (enter your login and password), both in KDE and in xfce.
I tried to remove the option "VGA = 773" from the boot parameter has the kernel (GRUB), and the problem with switching to the console was gone.
2. I made a nvidia-xconfig, creating a file /etc/x11/xorg.conf, rebooted (with the VGA = 773), and logged in to KDE user denis (yes my name is Denis too ), the name of my new account, the name of the old - user0), and the Problem with switching to the console was gone, at least for now.
I think that the Problem with chromium somehow connected with the fact that the video card is Nvidia and its mode of operation, which hurt when you log in to your account.
How does chromium in KDE in your account until Dennis, I have not tested that particular - will be tested, the result accomplish your goal.
So try to remowe vga=773 from kernel line, and and see how it will work chromium.
But i still dont know, why chromium work fine in xfce, but freezing in KDE...
Last edited by killer1804 (2012-03-01 06:00:05)

No web fonts working in chrome...how to fix?

Right now there is a bug in chrome where no web fonts are working...not even google ones
I have found a few fixes....just not sure how to implement them into muse
Fix 1
$('body')
.delay(500)
.queue(
function(next){
$(this).css('padding-right', '1px');
Fix 2
"I was able to find a css-only workaround that works for me at least. I only had problems with my p elements, so that's all I selected here".
p{
-webkit-animation-duration: 0.1s;
-webkit-animation-name: fontfix;
-webkit-animation-iteration-count: 1;
-webkit-animation-timing-function: linear;
-webkit-animation-delay: 2s;
@-webkit-keyframes fontfix{
from{      opacity: 1; }
50%{     opacity: 0.8; }
to{     opacity: 1; }
Fix 3
$(document).ready(function() { if (navigator.userAgent.toLowerCase().indexOf(‘chrome’) > -1) { var current_css = $(‘body’).css(‘font-family’); $(‘body’).css(‘font-family’, current_css);setInterval(function() { var current_css = $(‘body’).css(‘font-family’);$(‘body’).css(‘font-family’, current_css); }, 5000); } });
Any chance anyone can tell me how to implement any of these fixes into a muse site....the update of chrome also has the issue in it as well
Here is some links to the discussions
http://blog.typekit.com/2014/02/04/chrome-bug-affecting-web-fonts/
http://blog.typekit.com/2014/02/28/new-bug-in-chrome-v33-affecting-web-fonts/
https://code.google.com/p/chromium/issues/detail?id=336476#c30
Thanks

Firefox displays the content that Google sends to it. If they send worse content to Firefox then you will need to give Google feedback about it. I believe https://productforums.google.com/forum/#!forum/websearch is there feedback site.

Youtube html 5 problem on google chrome

Hi everyone i am new here.It took me 10 minutes to sign in to forums.So i am that good with computer
I want to show youtube videos on my blogsite where i write about taxi scams in istanbul but it seems like there is sound but no picture.It's the same when i go to youtube.
Some says to clear my cache and some says to change youtube to html5.I don't know anything about html or css.
Some easy solutions please?
Regards.

Hi,
The above URL gives a 404. But it seems you have moved the video to the homepage instead.
I'm able to reproduce the problem on Chrome.
However, I noticed that you are using video.js library for playing the video files. Have a look at the below thread for a possible solution posted by video.js community members that might help.
http://help.videojs.com/discussions/problems/1410-videojs-ajax-chrome-bug
Thanks,
Vinayak

Redirect Problem in Chrome

Hi everyone,
My site URL: www.ingeniodijital.com
Muse Version: CC 2014
Chome Version: 35.0.1916.153
Chome redirect to tablet version when I try to display on my desktop.
I read every post and I tried everything which were suggested and I have still same issue.
Please help.

Ahmic guy Yes, and at that time I replied with a link to a thread with more information and a link to the Chrome bug in Google's bug tracking system.
Historically, Google's been very quick to address bugs reported against Chrome. In this case, they have not been. The same thread I referred you to previously includes one customer's workaround for this Chrome bug <Re: Tablet version of website is showing up instead of desktop version in Google Chrome>.
Given how slow Google's been to address this bug, it's likely we'll make changes similar to that described by the customer in the referenced thread, though doing so will introduce the possibility that a small number of older tablet devices will suddenly start loading the desktop rather than the tablet version of sites.

Chrome bug?

Similar Messages

Maybe you are looking for