Don’t know if this is the case on other Android platforms or other Android web browsers…
The entire horizontal panel starting with the breadcrumbs on the left side is over-written on the line above (starting with New Posts). The result is that the breadcrumbs and most of the profile settings are not rendered, thankfully “log out” is visible.
So, it appears that the code used for the carriage return before rendering the breadcrumbs panel is “obviously” different than what is used everywhere else in the style sheet.
Edit Post - Upon closer inspection, the breadcrumbs are unreadable as described, but the User Settings is a different page element munged differently. In that case, only the first (Welcome, username) and the last (log out) are displayed. Everything else in that element is not rendered.
Although the specifics of my device and browser are relevant to the issue, I doubt that it’s relevant to the larger objective of ensuring consistent and proper rendering on all devices and browsers.
TSU
HTC T-Mobile 3G Slide
default web browser (HTC v7)
> Although the specifics of my device and browser are relevant to the
> issue, I doubt that it’s relevant to the larger objective of ensuring
> consistent and proper rendering on all devices and browsers.
>
> TSU
> HTC T-Mobile 3G Slide
> default web browser (HTC v7)
I see this as well with the default Android browser, but on FF on
Android, it works fine.
Chances are it has to do with the default browser not supporting HTML
elements used in the template.
But, as I noted I doubt that this is likely the only instance this problem will come up. Wouldn’t be surprised for instance if Android tablets become more popular this problem would be reported more often.
So as I noted, although other browser apps can be used I still think it’s a better idea to just fix the CSS code (It shouldn’t be that difficult, right? And, I wouldn’t consider this a high priority so it could be addressed “whenever” as long as it isn’t totally forgotten).
On 09/28/2011 05:16 PM, tsu2 wrote:
> I still think it’s a better idea to just fix the CSS code (It shouldn’t be that difficult, right?
i’m guessing the css code is part of the vBulletin package, and that
means everytime there is a vBulletin 'upgrade it would require more
fixing up…hey, perhaps you c/should log a bug with the vBulletin
folks…hmmmmm, but i guess first it would be best to make sure it is
not a flaw in the opensuse.org webmasters work, huh?
> And, I wouldn’t consider this a high priority so it could be addressed “whenever” as long as it isn’t totally forgotten).
there are already several things that are re-broken with each ‘upgrade’…
–
DD
openSUSE®, the “German Automobiles” of operating systems
> So as I noted, although other browser apps can be used I still think
> it’s a better idea to just fix the CSS code (It shouldn’t be that
> difficult, right? And, I wouldn’t consider this a high priority so it
> could be addressed “whenever” as long as it isn’t totally forgotten).
