Can anyone help here, i'm wondering if this is actually a bug or expected behaviour?
Chrome Dev Tools seems to not be allowing hovering elements and highlighting of them in Iframes over a certain height.
For example, look here:
http://csreis.github.io/tests/cross-site-iframe-simple.html
now if you set the iframe height to 3000px, and then go and try to inspect the 'Cross the bridge' button. It does not highlight or allow you to select anything below the container you can see about half way down the picture.
I am getting this same behaviour on a different project I am working on, where the highlighting is not working in dev tools in an iframe.
Is anyone else getting this behaviour? I am using Chrome 88.0.4324.190 and am seeing this behaviour on other machines too. I am not getting this behaviour using Firefox which allows me to highlight all elements in iframes. I'm stumped on this one.
Thanks.
Related
I am developing a static web app via React.js. I am using the google dev tool to inspect elements. In responsive design mode, everything is fine. However, when I select a specific mobile phone the footer element is not shown when I scroll to the bottom. However, it is visible on the console when ı inspect elements I can see the HTML info. I thought that maybe somehow I fixed the height for mobile devices or smt. Then I tried the firefox dev tool and I am able to see the footer. I have no idea which one is more realistic since I didn't deploy it yet. I deleted the history of browser before I tried.
More specifically; on the chrome dev tool when I select responsive design mode and change the resolution to 375x812 (same as iPhone X), I am able to see my footer. If I select iPhone x rather than responsive design mode, then I don't see it. It is more annoying that, both cases are okay for the firefox tool and I see my footer. So what is the problem ? Why two dev tools act so so differently for the same app and more importantly which one is true ?
Okay, I figured it out. There is a zoom option next to the width and height. It was 100% for my case, which should be "fit to window". I am leaving this dumb question here, it helps if any other beginner faces the same issue.
I recently tried to load a tool on my phone that I develop that is hosted internally where I work.
A few things looked off, which I expected. But one particular element seemed to be extra odd.
I eventually loaded the page in Chrome on a MacBook Pro and used the "Device Toolbar" feature to render it in my Desktop browser like it would on a phone. To keep a private application private I will demonstrate with Google.com. This is what I see:
That's the body element highlighted in blue. The html element is the same.
This is what I see in my application too and explains what I'm seeing when actually using my phone.
I can't, for the life of me, understand why these elements chose this size. There is no explicit "width" for these elements, nor is there "max-width" etc. Nothing that I can see that should cause this behavior.
Can anyone explain this behavior?
UPDATE
It appears that there is some odd behavior with Dev Tools. Proper mobile testing probably shouldn't be done this way (Feel free to change my mind, Google...) but the issue stands that sometimes, the body element doesn't stretch to accommodate its content.
By default, block-level elements, including <body>, do not expand to fit their content, but rather will expand to the width of its container. See the spec for detailed information.
See this fiddle demonstrating this. If you resize the panels/window you'll see the body width changing based on the viewport, but the content width has absolutely no effect.
This SO question has more information: Why isn't <body> expanding to fit its contents?
Another issue that's not helping is related to the Chrome dev tools device toolbar. Changing the zoom, disabling and re-enabling the device toolbar and its settings can be buggy and is not always reliable. I have spent hours chasing issues that didn't actually exist because the device toolbar functionality misled me.
I've loaded a page with multiple SVGs on chrome.
when I zoomin/out one of the SVG is disappearing and I have no idea why this is happening.
(and it stays like this even when I zoom back to default)
any ideas?
this is the url if you want to try it yourself
http://www.facegift.co.il/canvas/?userItemId=17887&sc=987404&print=1&width=1500&pageNum=7
This is not a bug in Chrome. This is a bug in your page.
All the id attributes on the page have to be unique. But on your page, they are not.
The <linearGradient> for that botanical flourish has the id "SVGID_2_". There is also a <clipPath> element on the page with id="SVGID_2_".
Fix that problem (and any other duplicate ids) and I am certain things will start working.
Then you should also delete your Chrome bug report.
I had a very similar issue in Chrome because one of the elemets had the transform attribute:
transform="translate(0,-9000000000)"
And it made Chrome go crazy. The solution was to hide or remove the element.
The HTML and CSS are rather large so I can't pinpoint the issue or post a good example. When I toggle through my UI, the css styling seems to break, the most jarring of which is that the background changes to grey. I was wondering if anyone encountered similar issues. Here are some of the conditions for me.
-Chrome: Firefox & Safari working fine
-Small Screen: Problem doesn't occur on larger monitors
-Toggling developer console on and off fixes the issue
It's difficult to try and pinpoint the issue without seeing some code or even a fiddle, but when you open the inspector the page is resizing, and so redrawing (at least some of) the elements. It's also possible that there's a cache issue - I believe by default when you open the inspector the cache is disabled and so all css and scripts are downloaded again. That said, if you aren't refreshing the page it with the inspector open its unlikely to be that.
My money would be on the window effectively resizing when you open the inspector, and so some (if not all) elements are forced the redraw and thus re-evelauate their styles.
Maybe you could use Chrome's timeline to check what is being painted as time goes by. Try running that and opening the inspector while its active to try and see whats going on.
Looks like a long standing bug (years) with webkit:
How can I force WebKit to redraw/repaint to propagate style changes?
The solution that appeals to me is:
$('#body').hide().show(0); from Force DOM redraw/refresh on Chrome/Mac
to force a redraw.
I am experiencing redraw issues in Chrome that I can't explain. They don't appear in any other browser. The website is http://leonardo.re
They appear after hovering over a styled DIV containing a styled link (contact page):
And sometimes on an overlaying DIV when scrolling (any page). Not always though:
Does anyone know what exactly is going on or how this can be solved / avoided?
This bug has now been resolved in newer versions of Chrome - no more issues!