Eclipse browser behaving different than standalone version - eclipse

I'm using the org.eclipse.swt.browser.Browser for a plugin and would like to dynamically include a font by adding #font-face css to head by using javascript.
I'm working on Windows, so eclipse will use the IE engine to render html. But: My solution works great on IE9 when running it in the standalone browser (also in chrome, opera, safari), but not when running it in eclipse.
The javascript is successfully executed, but fonts seem not to be loaded. Are there some security settings I should change on the Browser object? I didn't see such a method...
Btw, the font-face urls point to local font files. And #font-face works when defining it initially instead of dynamically loading it with JS.

Related

modified CSS3 codes working on IE, but not on Chrome

why does this happen? I'm using eclipse neon.1 and tried changing the color of the font in the CSS3 code and it worked on both internal browser and IE9, but not on chrome. I restarted the server a lot of times and even rebooted the computer but it still won't be applied on Chrome....
Right click on the text and go to inspect element, see if it shows newly applied style in styles section in developer tools. If not you may need to clear cache using Ctrl+Shift+Delete and reload the app.

Aurelia/Babel 6 sourcemaps shown as html

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.

Waiting mouse cursor in my GWT application stays infinitely (only in Chrome, only in Production)

Could you please tell me why I have waiting mouse cursor in my gwt application as if page not fully loaded ? It doesn't happen on dev server. It only happens in production. Also it's happening in Chrome but doesn't in IE.
Link to my app is here.
Screenshot
I checked it again in Chrome, but for me no wait cursor is Displayed. But i think, your Google Chrome is trying to open the Google Translate Menu. For me it came quickly and the page loading stopped and the mouse was at normal position.
I prefer you try updating your chrome.
I have also checked the same in my co-workers Laptop and its working fine too.
If problem still persists, please use CCleaner Software and clear all Temporary files, Browser Cache, Recent files etc. Why because, GWT creates a lot of temporary files which may reduce your system performance. So after each cleaning, just restart the system also. I had few such resolutions recently.
I opened your link in Firefox and got the following error
ERROR: Possible problem with your *.gwt.xml module file. The compile
time user.agent value (safari) does not match the runtime user.agent
value (gecko1_8). Expect more errors
This is because, you have compiled your code for Webkit browsers only. If you have added a line as below in your gwt module xml file,
<define-property name="user.agent" values="ie6">
you may either remove it or you can add more browser support via this.

Typekit fonts not working on some machines

We're using typekit fonts for some of our styles. We've noticed that on some machines, the fonts don't load on our live site, although they do on our dev site. This is only on certain machines, and only when viewing our live site (which is identical code-wise to dev at this point.)
For example, my boss looks at the dev site and the live site in two separate tabs in Chrome on the Mac. The elements using typekit fonts look different on the live site (they're failing over to the default serif font.) On my Mac in Chrome, everything is correct on both versions of the site.
Is there some kind of browser setting somewhere that would cause this? (Given that the fonts being used are barely distinguishable from a default serif font, my solution would be to just eliminate the typekit fonts altogether, but it's not my call to make.)
I'm not sure if this solves your issue, but my issue was that I was loading "Museo Sans", and I needed to load "museo-sans" for the css font-family. The first font-family was loading the font directly from my machine, so it worked on another designers machine who also had the font loaded, but not on most other devices/machines via typekit file.
Hope this clears up one potential scenario.

GWT -- Hosted mode fonts look larger than compiled version

When I create an application on my laptop it compiles and renders just fine. If I compile the page and put it on a server to host it, it still renders just fine on multiple computers.
However, if I transfer the code to my desktop and run it on my desktop the size of all the fonts is all messed up. Everything is MUCH bigger. As you can probably guess, this messes up my layout considerably.
On the desktop machine I am using the GWT browswer...
Any ideas on why the same code would render differently on two different machines?
If I compile the code on the desktop and put it on a server it looks like the laptop version (small).
Essentially I have this:
Laptop
Hosted: small
Server: small
Desktop
Hosted: large
Server: small
I have checked this against IE, firefox and safari.
Why does hosted mode look different?
Thanks!
Because you have different default font sizes and/or monitor dpi settings on the two machines?
AIUI the GWT standard styles just sets font size to "small", which will be relative to the default font size set in the browser. Either set the fonts to a measurement in pixels or, better, use a more liquid layout that can cope with a range of font sizes.
The GWT Debug browser uses the native browser on your machine (so IE on Windows, Safari on Mac, Firefox on Linux).
It's not a GWT issue, but some fonts look different in different browsers (even at the same size and style). You need to find a font and size that looks nice across all the browsers you want to support, and then set that as a css style for your text.
It is something to do with the Browser you used, the Browser on your desktop may have large font as preference set. Try restore default settings of that browser or try with other browsers.
I'm doing a project in GWT as well and am getting hit by this as well and here's my take....
[rant]
This whole html, css, javascript ball wasnt just randomly dropped...the mtha fcka was dropped from the fckng space station. You'd think with all the self proclaimed brainiacs out there working on this stuff there'd be a solution by now. There's a million frameworks out there that help avoid putting together a big slop but the fact is that spaghetti nightname started long ago and is beyond clean up and it's called html/javascript.
There's no browser standards. Some sites support only IE, and I'll get that box that says "Sorry, you must use IE" and then the neighbors have to hear me curse cause what are you supposed to do if you don't run Windows?
[/rant]