• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Fonts for outputText changed after upgrade javax.faces.jar from 2.1.6 to new 2.1.29

 
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

My environment is: NetBeans 8.0.1 + Glassfish 3.1.2.2 + JSF 2.1 + Richfaces 4.3.7 + CDI/Weld 1.1.8 (original) + Apache CODI 1.0.6 + JPA 2 + Hibernate 4.2.7 + RDBMS Firebird 2.5.2 + JasperReports 5.5.

Yesterday, I started tests after changing the original javax.faces.jar 2.1.6 that comes with Glassfish to the new 2.1.29 downloaded.

Then, the h:outputText labels from my webapp becames bigger.
All other components become exactly the same size.

Below sample attachments from the "old 2.1.6 page" and "new 2.1.29 page" in Firefox 33 and Chrome 39. Same behaviour in IE too.
Using Chrome, the difference in outputText is more visible.
The only change in my project was javax.faces.jar file.

JSF-Firefox-OutputText.jpg
[Thumbnail for JSF-Firefox-OutputText.jpg]
Firefox with old and new pages
JSF-Chrome-OutputText.jpg
[Thumbnail for JSF-Chrome-OutputText.jpg]
Chrome with old and new pages
 
Saloon Keeper
Posts: 27752
196
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Welcome to the JavaRanch, Edilmar!

h:outputText should not be setting any style info by default (unless something's been changed that I don't know about).

I recommend using your browser's page element inspection tool to see what styles have been applied and see if you can tell what set them.
 
Edilmar Alves
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I dont know if this is a bug in JSF 2.1.6 that doesn't recognize the font configuration from the browser and uses the configuration defined in my css file:



or newer versions of JSF uses the configuration from the browser and ignores the configuration defined in my css file.
 
Edilmar Alves
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Behaviour of formatting outputTexts:
- JSF 2.1.6: if I don't define a CSS style, it uses some internal default font size and not the font size from my "CSS body" general config
- JSF 2.1.29: if I don't define a CSS style, it uses the browser default font size and not the font size from my "CSS body" general config
Then, I was happy with internal font size from 2.1.6 that allowed the same layout at all browsers.
Now, with 2.1.29 I will have to configure a CSS style class at all outputTexts to ensure the same layout at all browsers.
 
Tim Holloway
Saloon Keeper
Posts: 27752
196
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
JSF doesn't "use" CSS at all. It just passes stuff along. The browser is responsible for dealing with CSS and there are very definite precedence rules.

Check the generated tags to make sure that there's a proper body HTML tag in the proper place.

The Firefox browser's Firebug extension will show what CSS has been applied from where and additionally illustrate what elements have been overridden.
 
Edilmar Alves
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Again... I made two tests:
1) creating a xhtml without Richfaces
2) creating a xhtml with Richfaces but without any Richfaces component
3) creating a xhtml with Richfaces like page above that uses many components with their CSS layouts

I created the outputText without style class, to use the default style defined.

- 2.1.6: same behaviour in 1), 2), 3)
- 2.1.29:
===> 1) uses my "CSS body" font config
===> 2) uses my "CSS body" font config
===> 3) uses browser default font config => this case I have to force a CSS style for all outputTexts, I think there is some CSS layout from Richfaces components that changes the default config and causes confusion for all the layout
 
Tim Holloway
Saloon Keeper
Posts: 27752
196
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
RichFaces is "skinnable". There are something like 5 basic skins shipped with RichFaces, with the BlueSky skin being the default (you can override this in web.xml).

So yes, RichFaces is almost certainly setting the page default font, weight, style, and point size, probably on the h:body element (another reason to use h:body and not just HTML BODY).
 
You have to be odd to be #1 - Seuss. An odd little ad:
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic