While testing my website on my LG VX8360 cell phone with Openwave Mobile Browser 6.2.3.2, I encountered a problem with CSS child selectors and descendant selectors. Despite specifying that only the second div should have a yellow background, both divs displayed as yellow. This inconsistency led me to seek out potential workarounds online but I came up empty-handed.
EDIT: I want to note that I am serving the page with a "Cache-Control: no-transform" header, ruling out any interference from proxies or transcoders.
I ran some tests following Felipe's suggestions with no success in isolating the issue. Even when altering the style application method, such as using inline styles instead of an external stylesheet, the problem persisted. The unexpected behavior even continued after defining different backgrounds for each div based on classes and ids.
Further experimentation revealed that applying the style directly to the inner div circumvented the problem related to child and descendant selectors. Changing character encoding and removing meta tags had no effect. External CSS files caused issues as well - while linking them worked normally, @import statements failed to render any styles.
The deeper I delved into this issue, the more intricate it seemed. Despite considering buying a new device, I aim to ensure my site functions seamlessly across various internet-enabled gadgets. Frustrated by the lack of definitive information about the browser's CSS support, I feel perplexed about finding a solution.
EDIT 2: Instead of resorting to purchasing a new phone, I strive to create a universally compatible website without compromising design aesthetics.
EDIT 3: Despite consulting resources like this guide on mobile CSS compatibility, I found no reference to my particular browser version. Next, I plan to explore relevant blog posts for insights.
EDIT 4: Researching extensively yielded limited information on which CSS features are supported by the browser and how to address associated challenges. Although tempted to dismiss this due to the browser's obscurity, recent encounters with newer phones exhibiting similar behaviors prompt me to tackle this issue head-on.