I am compiling web pages and am frequently specifying multiple elements in class names. Example: class="flatall red1". In most cases, this seems to work fine, but the following combination is giving me trouble:
class="slink1 slink1roundall btnmod"
This works fine on all browsers, but not when compiled with Phonegap and run on an Android device (hasn't been tested on ios or winphone, btw)
border-bottom: white 1px solid;
border-left: white 1px solid;
border-top: white 1px solid;
border-right: white 1px solid;
font-family: 'Segoe UI' , Verdana, Arial, Helvetica, sans-serif;
background: -webkit-gradient(linear, left top, left bottom, from(#357db2), to(#357db2));
background: -moz-linear-gradient(top, #357db2, #357db2);
filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#357db2', endColorstr='#357db2');
The element (button) shows the correct background (.btnmod) but fails to display as flat with solid white border and white italic, lowercase text.
Instead, it displays as a standard "raised" button with white border on the top and left sides, gray border on the right and bottom sides, black text, non-italic, upper and lowercase...
Can anyone shed some light on my error, please?
Can anyone help with this?
Hard to debug and find the root problem without creating such app, first. I would guess that the Android default webview doesn't like a specific combination of attributes and values that you are using.
However, you might try that yourself: keep the .slink class as is, but remove the other parts. See if it shows your flat UI with proper font.
If it does, add the other classes step-by-step, until it fails. Then remove each attribute of the lastly added class one by one to find to 'bad' part.
Other process steps are feasible as well...the whole idea is to isolate the attribute combination that causes trouble.
(of course, I'm assuming that you haven't defined any of the css class definitions twice in your code, with conflicting attribute values; you should check that, though)
Alternatively, you could consider using the Crosswalk webview (you'd need the crosswalk plugin) and see if it works fine there.