Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    Tahoe - Corbel font sometimes bugged in Firefox 55.0.3 (32-Bit)

    Hi there,
    we have received multiple screenshots from our customers, that the font on the buttons is hard to see.
    Requesting a screenshot from the customers was sucessfull. Also we have asked for the OS and it was "Windows 7 Ultimate SP1".
    At one customer this issue has resolved by it's own (without changing anything) the next day, but we received some other feedbacks which results into the same bug.

    This is a part of the screenshot we have received from our customers:

    This is how it should look like:


    Do you have any clue why the corbel font is displayed so "demolished" ?
    It seems the font can be used from the browser, so also solving this issue, for alternative fonts, wouldn't solve this displaying issue.

    Best regards

    p.s. we have edited the background-color of the buttons slighty, therefore the blue is a bit darker than the original blue.


    #2
    Can you confirm that it *is* the corbel font, and not "corbel-bold"?

    Also, what kind of buttons are they?
    Last edited by Isomorphic; 8 Sep 2017, 01:19.

    Comment


      #3
      Hi there,

      It's a normal Button within a Toolstrip.
      We haven't changed the font of the buttons, so the normal declaration .button (" font-family: corbel;") is used, so one of the corbel fonts ("fonts/corbel.*") should be used. Because there is no alternative font (no second font in font-family) only the corbel font is used.

      Code:
      isc.Button.create({
          "ID": "openAssistentButton_2",
          "click": function () {
              clickTransportEvent(this, "2", "5", "...");
          },
          "accessKey": "a",
          "overflow": "visible",
          "tabIndex": 0,
          "hideUsingDisplayNone": false,
          "title": "Assistent&nbsp",
          "hiliteAccessKey": true,
          "showDisabledIcon": false
      })
      Best regards

      Comment


        #4
        Have you seen that it's using corbel at the same time as seeing the bad font?

        If not, what's the build-date of the version your users are running?

        If it's older than 2 or 3 weeks, you'll need to update them to the latest from smartclient.com/builds, which includes some recent changes - your image looks like it's showing helvetica-neue-bold, rather than corbel - and the former has been removed from the skin in recent builds.

        Comment


          #5
          The its all "bad font" or corbel. We haven't seen any feedbacks with both "fonts".

          The build we are currently using in our production system is v11.1p_2017-08-08/Pro Deployment.
          So, yes it's older than 2 or 3 weeks. We can switch the version but are doing this with care. If there is a new bug in a smartclient we haven't seen this bug could stop our customers from using our software.

          Thanks for the tips, we will deploy a new smartclient release as soon as the issue with the new chrome version is fixed (https://forums.smartclient.com/forum...-latest-chrome).

          Best regards

          Comment

          Working...
          X