The charts, especially when exportedToImage are oversized/scaled - discovered on a MacBook in Chrome and Safari - while testing for an issue with Primefaces (Pf uses JqPlot for charts)
See on the jqplot test-page, but it is also reproducible on Linux/Ubuntu with a Chromium-based browser when opening developer tools and selecting any mobile-device (in this case I set it to "responsive")
!! - reload the page after opening dev-tools !! - at any resolution the image keeps getting oversized. To disable the effect, just close dev-tools and reload. Now the image looks correct again.
There was an issue on GitHub, but it was closed.
Also the showcase of PrimeFaces using this library works.
How can that be? I've checked this with all my available devices to rule that out - but it's somehow strange - can someone also reproduce this?
What does developer tools and Chromium on Mac do to get these results? - ignoring media-queries? I've also experimented with that, no success.
If your read that jqPlot ticket you posted here it has a solution in it: https://github.com/jqPlot/jqPlot/issues/119
PrimeFaces 8.0 Showcase has the following manually patched fix applied from that ticket:
https://github.com/primefaces/primefaces/issues/4655
That is why the PrimeFaces showcase does not exhibit the issue if you read through that ticket it is a two line fix applied to the JQPlot code.
Related
I am new to Karate UI and trying to maximize the chrome browser using Karate ZIP release(0.9.6RC4) on mac
I tried both with no luck
Given driver 'https://google.com'
And driver.maximize()
And maximize()
However fullscreen() is working fine, kindly help
Sorry it seems to be a bug in Chrome itself. You can try this experiment:
* driver.send({"method":"Browser.setWindowBounds","params":{"windowId":1,"bounds":{"windowState":"minimized"}}})
Now replace minimized with normal or maximized and you will see maximized does not work. But it is supposed to as per the spec: https://chromedevtools.github.io/devtools-protocol/tot/Browser/#method-setWindowBounds
This definitely used to work in previous versions of Chrome :)
We don't consider this a priority, feel free to raise a feature-request and also investigate if there is a known problem with Chrome. So I put the question back to you "kindly help". We need more open-source users to contribute.
Also note that driver type chromedriver works fine.
I have an aurelia application updated to the latest beta, 1.0.0-beta.1.2.1 at the time of this writing. This version of aurelia already uses Babel 6, and my application is based on the based on the ASP.NET 5 ES2016 navigation skeleton.
"All of a sudden", whenever I try to open my untranspiled javascript source files in Chrome (Version 49.0.2623.110 m (64-bit)) Developer tools, for instance main.js, all I get to see is the html of Index.cshtml.
It doesn't matter which javascript file I try to open, it always shows the html of Index.cshtml instead of javascript.
The transpiled files are displayed correctly in Chrome Dev Tools.
I've had this before but it usually meant I had a binding or templating error somewhere, but in this case the application works perfectly, so it probably has to do with the sourcemaps... Or does it?
My questions are:
What is the best way to track down a subtle binding or templating
error in Aurelia? Everything I've tried to do in my applcation works
fine, but I don't want to rule out this being my own fault just yet.
In case it's not my fault, has anybody come across this before? What
is the reason the sourcemaps are not working; is it Aurelia? is it
Babel 6? Is it Chrome?
Update
It doesn't seem to be a Chrome issue; the same problem occurs in Edge.
Update 2
By turning off Enable javascript sourcemaps on Chrome Developer Tools I can debug de transpiled code.
The transpilation gulp tasks I'm using are copy/pasted from the version mentioned above.
Has anybody else come across this issue?
Ok, I think I've found the problem.
I changed includeContent to true for sourcemaps.write in the build-system gulp task defined in build\tasks\build.js, so that line 23 of that file looks as follows:
.pipe(sourcemaps.write({ includeContent: true}))
This comes set to false in the navigation skeleton, so more people should have this same issue. Anyhow, this seems to have solved the problem.
I also removed the sourceRoot: "/src" parameter in that call, as it is only necessary when includeContent is false.
Starting a couple of weeks ago....on some of our sites, but not all, when inspecting an element, the styles tab only shows the "styles box", but not the actual styles relating to css?? - Again, this is ONLY on some sites - weird
It should look like this (with styles showing on the right relating to css)
BUT......instead, on SOME of our sites, this just started a couple of weeks ago looking like this....with no css showing in the styles tab:
NOTE: it has worked for 2 years - The page looks fine and all styles are being applied to the DOM, but do NOT show up in the styles tab when inspecting element.
Any ideas??
I just had this same issue and to resolve it I went into Chrome Developer Tools -> Settings -> Scroll to the bottom and click "Restore defaults and reload" then it all magically came back!
I hadn't changed anything between it working and when it stopped so not sure why it broke but hopefully this helps you too.
I just close the tab, and reopen it, and then right click > inspect element. Don't need to restore the whole dev tools to default settings. It's a waste. Try it, it works! :)
I had to go to Chrome Developer Tools -> Settings -> Enable JavaScript source maps and then disable that checkbox. It has probably got do with sourcemaps and the fact that I'm building the scss to css.
something that worked for me: chrome:flags>Enable Developer Tools experiments>Disable. I had enabled it at some point, used it for years w/o issue, then could not see any style details as OP described. After updating, resetting devtools prefs to default, even trying incognito, this was the one thing that seemed to get it working again. There were some neat experiments, but i'd much rather be able to do my job...
I was also facing this problem, in addition to the suggestions the other users made it worked for me accessing:
Chrome Developer Tools -> CSS -> Relaoad Linked Style Sheets
Image Ilustrating the procedure
Another one for the mix - using CSS variables but one of the variables was referencing another variable that didn't exist.
Elements using that missing variable in the chain just don't show up in chromium at all (it hid all references to h2s in the case of my site).
Interestingly, it still shows the elements in Firefox's dev tool panel.
Look for errors in the CSS file, in my in my case it was on the global CSS variables, fixing the errors solved the problem.
This tool can help you find the errors:
https://jigsaw.w3.org/css-validator/
I was just having the same odd issue. I'm not 100% sure what triggered this to happen but we use build tools to build SCSS into CSS. I went into my CSS file and removed the source map reference -
/*# sourceMappingURL=myCSS.map */
And all of the sudden it started showing up again. Then I added it back and I can still see it. I am not sure if this is because a version of the map is cached now or not but this worked for me.
Even i faced this issue !!!
style.css file was causing this issue..
I just created a new css file (Ex: style1.css) and cut pasted the older css file content (all lines in style.css) to style1.css file. It works
Note: Don't forget to update link tag, which is loading css file.
I think your CSS files are not loaded properly. Just check the syntax for referencing the external stylesheets.
It should be like this
<link rel="stylesheet" type="text/css" href="mystyle.css">
If you are skipping the rel="stylesheet", browser may think it as a plain file. To confirm the loading of stylesheets go for Chrome Inspector -> Sources
Check the site resources
No need of resetting anything. Hope it helps :)
I use Dreamweaver and Breckets.
Could see that the problem occurred only when I used Dreamweaver.
Solved the problem by changing Dreamweaver's preferences
--> Code Format --> Line Break Type --> CR LF (Windows)
Sometimes it can be the server!
I just had this error on a page that appeared to be fully loaded but the style panel was completely empty.
A complete restart of Chrome (and verifying no processes) did not work.
Restarting my server (in this case a .NET Core app running locally in Visual Studio) then allowed the style panel to show.
I think there was some sort of connection leak or web socket limit - something of that nature which was confusing Chrome.
I think this may helpfull.. If it is an angular project > then simply run
ng serve --extract-css.
I was using IE10 on Windows 7 but it is such a buggy piece of you-know-what (hanging, crashing, etc.) that I gave up and installed IE11. It has not hung or crashed since installing. But I hate the F12 developer tools! Okay, not completely - there are some very cool new features. What I don't like is that they seem to have dropped several features that I really liked! Unless I'm just missing something... I've searched and searched on Google and Microsoft but all of the help I've found only describes the new features. Here is what I'm missing: Color picker, Ruler, and most of all, the Clear browser cache for this domain. They allege to have a Clear browser cache function, but it doesn't work! So when I make changes to my website, in particular changing graphics, the only way I can see the change is to delete all my temporary files from IE. Then I lose all of my cookies e.g. for automatically logging in to Stack Overflow! IE version 11.0.9600.16428 on Windows 7 Ultimate 64-bit.
The color picker is still available, go to the DOM Explorer tab and there is an eye dropper on the tool bar at the top towards the left. That activates the color picker.
For the issue of serving cached files try toggling on "Always refresh from server" on the network tool (3rd option from the left). This should get you the latest changes from your server.
I'm running Plone 4.1.4 and when I try to edit a text area that used to display the tinyMCE editor all I get is a dialog box listing a dict of "valid elements". I installed the kupu editor and that works fine, but I prefer tinyMCE. Has anyone run in to this issue? Any help would be greatly appreciated.
Browser and version? IE 9 has TinyMCE issues, and requires you to use a development release.
To get around it I had to install a version from github. If you have mr.developer, use:
Products.TinyMCE = git https://github.com/plone/Products.TinyMCE.git branch=GSOC-3.4.x
I have come across this problem as well. In my case I updated Plone 4.1.2 to Plone 4.1.4. The rich widget will not show the TinyMCE editor when the content type has just been added. But after saving the content type and then editing, TinyMCE would appear as expected.
The weird thing is that if you add a new Plone instance and then activate and add your custom AT content type. TinyMCE would render fine on your text fields.
A work around that seemed to solve the issue is to go to portal_setup and on the upgrade tab, select Products.TinyMCE:TinyMCE to upgrade. It would show that the profiles (version 3) on the ZODB and the filesystem are in sync. You can downgrade by clicking on "show old upgrades" and running upgrade profile 1.1->2. This worked for me but please try this on a development instance.
This looks exactly like a problem I had a few days ago. Are you using IE7 or below?
Though I don't know if this is the right way to go (more experienced devs, please advise), this is what I did:
(Assuming a windows box... )
Stopped the plone services
located the file on the filesystem called tiny_mce_init.js (in my case c:\Plone41\eggs\products.tinymce-1.2.10-py2.6.egg\Products\TinyMCE\skins\tinymce\tiny_mce_init.js)
go to line 93 (in my case this contains:
media_strict: false,
remove the comma resulting in media_strict: false
save the file
restart the services
Looks at Thariama's answer here.
I had the same problem (with IE and FF). It looked like the archtype installation was the problem.
After changing the order unter "ZMI->portal_skins->Sunburst Theme" (putting tinymce above archetypes), TinyMCE worked.
(http://plone.293351.n2.nabble.com/Tinymce-not-working-after-custom-type-is-installed-td7566873.html)