getmdl.io input underline issue with material form - material-design

I am using getmdl.io Material forms. The form was working fine. But some browsers are now not showing the underline.
Was working fine until yesterday. The issue is only on some chrome browsers.

Ok. I was able to find a solution to it. Basically it seems the new chrome version
Version 61.0.3163.100 (Official Build) (64-bit) is sometimes not recognising the border value in REM. So 0.0625 rem is not recognized.
When I changed it to 1 px. It sharted showing.
Hope this help others.
Vipin

Related

Text rendering bug in Safari?

For some crazy reason, there are these boxes that are showing up on line breaks within text on a site that I am working on within Safari version 6.0.3 (8536.28.10) (see attached screen shot)
I've tested this out on a different Mac running the same version of Safari and I cannot replicate the issue. So, I am not sure what could be causing this issue. Both Mac's are running up to date versions of Mountain Lion. So far it only seems to appearing on one particular Mac.
The font on the site is using a Google font called Source Sans Pro.

IE 7.0.5730.13 Problems with JSF Primefaces

I've created an application using Primefaces. It works well on Firefox, Chrome and IE 9.
But there are many issues using the application on IE 7.0.5730.13.
I'll list some problems:
DialogBox opens after clicking twice on a Button and page refresh
DropDownBox is just a gray box, only after clicking on it the list opens, it just don't looks like a standard DropDownBox
Tree table does not look well, some nodes pass over the tree table and just hang there
It looks that Primefaces is not compatible with IE 7.0.5730.13.
I researched a lot, but couldn't find anything on that issue.
Thanks in advance.
EDIT
For all those, who still have problems with Dialog Boxes in IE Browsers
remove "modal=true"
set a fix width for your dialog box
set a fix height for your dialog box
For the most part you are correct, PrimeFaces and most any JSF component framework is not compatible with IE7. Furthermore there are a few more advanced JSF components that utilize HTML5 features and may not work correctly in IE8 as well.
On that note, IE7 is an ancient browser and it is ridiculous if your client insists on support for it. If they must use IE7 for some proprietary legacy software then you can always suggest using a proper browser for your software instead, like any supported version of Firefox, Chrome or Safari.
Primefaces is supposed to support IE 7 until version 3.5 (which is not supporting it anymore). If you are using this version just downgrade it to previous one. However, I can't be more agree with #maple_shaft.

OpenLaszlo DHTML InputText issue with clickthrough in Firefox 15

For some reason i am not able to enter any text in inputtext in dhtml environment. The same is working fine in swf10 environment.
When i hover over the input text i observed that the cursor is not changing to selector. It looks as if the onmouseover event of inputtext is not getting fired.
Has anyone come across this kind of issue in openlaszlo dhtml envrironment?
I am using OpenLaszlo 4.9, Windows 7 and the browser is Firefox 15.0
I found a bug report in jira http://jira.openlaszlo.org/jira/browse/LPP-9934.
Please suggest any ideas to overcome this issue/
The problem you are seeing is probably connected to the way OpenLaszlo replicates the behavior of clicking through Sprites or visual elements in the Flash runtime for the DHTML/JavaScript runtime. Until recently browsers didn't support that kind of functionality directly. Therefore the OpenLaszlo team had to use a workaround, which is described in detail in this comment on LPP-5447.
Clickdivs exist to have independent control over clickable sprites,
without interference from regular divs. They are placed in a separate
copy of the regular lzdiv sprite hierarchy so we have more control.
This also provides a place to put focused inputtext divs so they are
in the foreground and clicking/dragging to edit works properly.
The clickdiv functionality seems to be broken from time to time with browser updates or due to regressions. In 2012 some improvements to the DHTML runtime click-through functionality were done, using newer browser features in Firefox (which now allows to click through div elements using the CSS style pointer-events). Since the clickdiv functionality is part of the LFC, fixing that functionality in your application is not advised.
You can test if the inputtext works by tabbing through the components until your inputtext element has the focus and start typing. If the text can be entered as expected, but you cannot click the component with your mouse to select it, it's definitely a clickdiv problem.
Update: Tested with OpenLaszlo 4.9.0 and various browsers
I've tested with OpenLaszlo 4.9.0, DHTML runtime and IE9, Firefox as well as Chrome, using the test case attached to LPP-9934: All browsers show that specific bug behavior. If the bug has not been filed, please file a JIRA bug.

Opera Drop down menu hover issue

I have just created a dropdown for my site. It works fine in all other browsers except new version of opera that is 12.02.
Webiste Url : http://www.sktechnologyworld.com/demo/anything/
Here when you mouse over on "Categories", it displays dropdown of that categories then when you hover on categories then it displays subcategories of that category. At this time there is background line remains at top of that perticular category and this same thing in all the subcategories. However when i open dragon fly in opera by pressing ctrl+shift+I then it works fine but if dragon fly is not open then it makes it weird.
Its very strange and have not face this kind of problem before. Any help?
Thanks
This is indeed a bug in Opera. As it's merely a cosmetic issue with no big impact on functionality I suggest you just report a bug to Opera Software and forget about it until it's fixed :-)
The root cause is that Opera fails to draw the background colour of the padding-top of the A elements correctly. It's mainly triggered by the padding-top:9px instruction on #CategoriesBar .nav. However, trying to work around it means adding hacks to your CSS and that makes it harder to understand and maintain - even more likely to break in future browsers. Hence reporting a bug and not trying to work around it is your best way ahead.
Here is a simplified demo you can refer to when reporting the bug:
http://jsfiddle.net/sNHbB/
Please let me know the bug reference number and I'll give it a kick for you.

Google Maps api v3 - Controls hidden in default tablet Android browser

I found strange problem. I used this basic example of google maps. This maps works on all browsers except on default browser in my Samsung GalaxyTab (Honecomb 3.1). In this browser there are hidden controls. Or controls have bad z-index. If I move with map, I can see them for a while. There is no problem in default browser in Android 2.3, in Firefox on tablet, or any other browsers. Does anyone have solution for it?
Thanks!
I discovered this bug today as well, but I'm trying to get an element float on top of a google maps element. I found a fix at: https://github.com/CloudMade/Leaflet/issues/335 and that is to add:
.gmnoprint {
-webkit-transform: translate3d(0,0,0);
}
This forces the element to be on top, for some really odd reason. The line above works for the built in zoom controls etc on my Samsung Galaxy Tab 10.1 and can of course be applied to all elements that should be on top.

Resources