FLUID-885: Font styling displayed differently in edit vs non-edit mode

Metadata

Source
FLUID-885
Type
Bug
Priority
Major
Status
Closed
Resolution
Fixed
Assignee
N/A
Reporter
Justin Obara
Created
2008-07-10T13:34:11.000-0400
Updated
2011-01-04T13:34:21.536-0500
Versions
  1. 0.1
  2. 0.3
  3. 0.4beta1
  4. 0.4
  5. 0.5beta1
  6. 0.5
  7. 0.6beta1
  8. 0.6
  9. 0.7
  10. 0.8
  11. 1.0
  12. 1.1
  13. 1.1.1
  14. 1.1.2
  15. 1.2
Fixed Versions
  1. 1.3
Component
  1. Inline Edit

Description

When editing the text in an in-line edit field, the text appears correctly in Lucida Grande font (e.g. &); however, it is displayed with a different font style. Copying and pasting the incorrect style into another program (e.g. ms word) shows the correct font.

Steps to reproduce:

1) open the inline edit demo page from the daily build site
http://build.fluidproject.org/fluid/sample-code/inline-edit/announcements/announcements.html

2) Edit one of the in-line edit fields by replacing the text with an '&'. Notice the font.

3) Press 'enter' on the keyboard to close the edit mode. Notice the font styling has changed.

This also effects the display of non-standard characters. You can find some here:
http://www.alanwood.net/unicode/miscellaneous_symbols.html

Environments

FF2, FF3, Opera 9.6, Safari 3.2 (Mac OS 10.5)
Safari 3.2 (Mac OS 10.4)
FF2, FF3, IE6, IE7, IE8, Opera 9.6 (Win XP)
FF3, IE7, IE8 (Win Vista)
IE6 (Win 2000)

Attachments

Comments

  • Justin Obara commented 2008-07-10T13:40:27.000-0400

    'screenshot-1' shows how the '&' symbol looks in edit mode

  • Justin Obara commented 2008-07-10T13:41:11.000-0400

    'screenshot-2' shows how the '&' looks outside of edit mode

  • Justin Obara commented 2008-07-10T13:43:57.000-0400

    'screenshot-3' shows an example of a non-standard character/symbol in edit mode. It's supposed to be a smiley face.

  • Justin Obara commented 2008-07-10T13:45:37.000-0400

    'screenshot-4' shows the same non-standard character/symbol as 'screenshot-3', but this time out of edit mode. Notice how it's now represented by a small square.

  • Anastasia Cheetham commented 2008-07-11T19:57:38.000-0400

    Daphne, could you try this out, and see what you think? Is this an issue? It's probably a side effect of the font that this sample page uses, but let me know what you think.

  • Daphne Ogle commented 2008-07-14T19:52:38.000-0400

    This is weird. The "&" is particularly handled bad here. I can't figure out what font it is being displayed in. The real problem is that, at least to me, it doesn't even look like an ampersand in the font it's displayed in.

    While checking this out I found that the edits are happening in a different font generally than display. So on the daily build site Justin points to, the text is displayed in Times but when edit mode kicks in it displays in Arial. In this particular case it isn't a big deal but will be when users are editing formatted text. We know users want a wysiwyg interaction.

    I'm attaching a screen shot that show the 2 different fonts.

    Can the component know what font the application is using for display of that field and use the same?

  • Daphne Ogle commented 2008-07-14T19:54:12.000-0400

    screen shot showing different fonts used in display versus edit mode.

  • Daphne Ogle commented 2008-07-17T17:50:42.000-0400

    Another complication with the different display versus edit font is that the text is larger than the edit field so the user can't see all the text they want to edit once they are in edit mode. I'm assuming we are calculating text field size based on the text pre-edit. This doesn't seem to happen in Safari only in Firefox (both on macs, not sure about PCs)

  • Justin Obara commented 2008-08-26T09:36:39.000-0400

    The font styling issue does not seem to occur in the bspace example (http://build.fluidproject.org/fluid/sample-code/inline-edit/section-info/section-info.html), or it could be that the font styling is similar.

  • Justin Obara commented 2008-10-31T09:34:11.000-0400

    design-watched

  • Daphne Ogle commented 2009-03-13T15:16:38.000-0400

    Unassigning so this can go into the development pool of bugs.

  • Jonathan Hung commented 2011-01-04T13:26:40.687-0500

    This issue is covered by the Simple Inline Edit Test plan.
    Infusion 1.3 release testing did not reveal any issues related to mis-coding of characters.

  • Jonathan Hung commented 2011-01-04T13:34:21.530-0500

    Fixed in Infusion 1.3.