Skip to content

ILLiad Known Issues

← Atlas Systems

Search known issues

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

61 results found

  1. Default FAQ web page contains inaccurate information about cookies

    The default FAQ web page contains information about cookies stating that "the technology that we use sends a Session ID to be stored on your machine. You can refuse this cookie and still be able to use ILLiad without any problems."

    This information is inaccurate as the Session ID cookie is essential for the ILLiad web interface.

    Bug# 18265

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  2. The <u> tag is used incorrectly in certain ILLiad web pages

    Several ILLiad web pages contain incorrect usage of the <u> tag to emphasize text where a <strong> tag should be used instead.

    Bug# 17980

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  3. Transaction menu buttons are inconsistent with other buttons in the web interface

    Some buttons used within include_TransactionMenu.html do not blend in well with other buttons in the web interface due to unexpected rounded borders or extra spacing.

    Bug# 17956

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  4. Certain fields marked as required in WebValidation table are not labeled as required in default web pages

    The following fields are marked as required by default in the WebValidation table, but are not marked as required in the default web pages on certain forms:

    -The PhotoJournalInclusivePages field is missing a required label on the LendingGenericRequestArticle and EditLendingGenericRequestArticle forms

    -The Department field is missing a required label on the NewUserRegistration and NewAuthRegistration forms

    Bug# 17645

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  5. Default search results text does not meet color contrast requirements

    The default color of the text used for the "No search results" message displayed when no search results are found does not meet color contrast requirements with the default background color of the web page.

    Bug# 17644

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  6. Focus indicators for interactive controls do not meet contrast requirements

    The focus indicator for several interactive controls in the default web pages (e.g., input fields, buttons, etc) does not meet the minimum contrast required by WCAG.

    Bug# 17641

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  7. Keyboard controls cannot be used to dismiss cookie notification popup

    Keyboard controls cannot be used to dismiss the cookie notification popup in certain web browsers.

    Bug# 16534

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  8. Incorrect anchor tags on include_notification_preferences.html may cause accessibility issues

    The "All" and "None" input buttons inside the includenotificationpreferences.html file are nested within <a> anchor tags, which is unnecessary since both elements are interactive by default and may cause these buttons to be flagged by accessibility validators.

    Bug# 16533

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  9. Web pages may not allow zooming in and out on some mobile devices

    The <meta> tag that is included on the include_head.html and LendingLogon.html files may prevent users from zooming in and out on the ILLiad web pages on some mobile devices.

    Bug# 16529

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  10. EditPatentRequest.html contains incorrect error parameter for PhotoJournalTitle field

    The error parameter for the PhotoJournalTitle field on EditPatentRequest.html has an incorrect value of ERRORLoanAuthor in the ILLiad 9.1 web pages. The correct value for this parameter is ERRORPhotoJournalTitle.

    Bug# 14817

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  11. Value persistence (persistedValue) does not work on Safari (WebKit) browsers

    Values will not persist properly when using Safari or any other WebKit-based browsers.

    Workaround: Add the following code to line 52 of atlasUtility.js within the block of code handling persistedValue:

    $(this).find("option[value='" + persistedValue + "']").prop("selected", true);

    Bug# 14597

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  12. Empty heading elements are possible in datarow templates

    If a transaction doesn't have value in the Title field, Author field, or any other field encased in a heading element (h4,h5, etc) on a datarow template, then the heading will appear empty in the web pages and cause confusion for screen reader users.

    Bug# 14456

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  13. The colors set for small notes, required text, and <p> tags in the default CSS do not meet color contrast requirements

    The colors set in the default CSS for "small-notes," "req," and <p> tags do not meet the WCAG AA accessibility requirements for color contrast.

    Bug# 14424

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  14. The role="heading" attribute on top level <div> containers may cause issues for screen readers

    The role="heading" attribute on the <div> containers surrounding most web pages can cause strange behavior with screen readers depending on the content of the file.

    Bug# 13849

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  15. Radio button controls on ViewSearchResults.html are improperly formatted

    The width: 100% property in the default CSS for label elements results in improper formatting/alignment for the radio buttons on ViewSearchResults.html.

    Bug# 13557

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  16. The "Cancel - Return to Logon" button on the NewAuthRegistration.html page doesn't return users to the logon menu

    Clicking the "Cancel - Return to Logon" button on the NewAuthRegistration.html page doesn't allow users to stop the request form and return to the logon menu.

    Bug# 12648

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  17. Unencoded ampersands in ILLiad 9.1 Default Web Pages

    A number of href attributes for <a> tags in the ILLiad default web pages improperly contain unencoded ampersands.

    Bug# 11203

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  18. Item Author appears twice in include_detailedTransactionInformation.html

    In the include_detailedTransactionInformation.html default 9.1 web page, Item Author appears twice:

    Item Author <#TRANSACTION field='PhotoItemAuthor'>
    Item Place <#TRANSACTION field='PhotoItemPlace'>
    Item Publisher <#TRANSACTION field='PhotoItemPublisher'>
    Item Author <#TRANSACTION field='PhotoItemAuthor'>
    Item Edition <#TRANSACTION field='PhotoItemEdition'>

    Bug# 10618

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  19. Duplicate classes on Lending pages

    ILLiad Lending datarowDefaultRequest and includeTransaction menu contain duplicate classes.

    Bug# 10147

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  20. Empty persist value string

    An empty string would be produced when the persist value drop-down in the atlasUtility.js due to the handling of the double-quotes.

    Bug# 10061

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →
2 4

ILLiad Known Issues

Categories

Feedback and Knowledge Base

(thinking…)