Skip to content

Settings and activity

5 results found

  1. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Derek S. shared this idea  · 
  2. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Derek S. shared this idea  · 
  3. 12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Derek S. supported this idea  · 
  4. 45 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Derek S. commented  · 

    Agreed. HiDPI screens are very common and automatically enhancing thin lines creates a negative end-user experience. For example, one has to explain that "it doesn't really look like that" when using a PDF. This affects many types of documents, including detailed illustrations.

    This should be kept as an accessibility option, however, not as the default.

    Derek S. supported this idea  · 
  5. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Derek S. commented  · 

    @Bilal's response seems to "fix" the issue, but I'm voting for this because this UI setting is extremely unintuitive when working with files that are not part of a scanned document workflow. It is not likely that user would use an OCR setting for a document that did not originate from a scanner.

    Additionally, this setting should be something that should be set globally, vs. per document.

    Derek S. supported this idea  ·