ILLiad Known Issues
54 results found
-
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 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in ILLiad v9.2 default web pages on August 30th, 2022.
-
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 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in ILLiad v9.2 default web pages on August 30th, 2022.
-
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 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in ILLiad v9.2 default web pages on August 30th, 2022.
-
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 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in ILLiad v9.2 default web pages on August 30th, 2022.
-
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 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in ILLiad v9.2 default web pages on August 30th, 2022.
-
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 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in ILLiad v9.2.1 default web pages on June 14th, 2023
-
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 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in ILLiad v9.1 default web pages on February 14th, 2022.
-
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 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in ILLiad v9.1 default web pages on February 14th, 2022.
-
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 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in ILLiad v9.1 default web pages on February 14th, 2022.
-
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 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in ILLiad v9.2 default web pages on November 22nd, 2022.
-
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 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in ILLiad v9.1 default web pages on August 31st, 2021.
-
Duplicate classes on Lending pages
ILLiad Lending datarowDefaultRequest and includeTransaction menu contain duplicate classes.
Bug# 10147
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in ILLiad v9.1 default web pages on August 31st, 2021.
-
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 votesReleased in the Default Web Pages on January 22nd, 2021
-
Fields marked as none when they should be hidden
On user pages, delivery methods and "web" fields are set to display 'none' when the correct attribute needs to be:
<input type=hidden...
Bug# 8653
0 votesReleased in v9.1 web page changes on 11/23/2020
-
Extra undelete icon in Action menus
There is an extra span in include_TransactionMenu.html and any HTML files with the undelete button in the Templates folder.
Workaround- change this:
<a class="btn btn-light <#TRANSACTION field='RequestActionAllowed' name='UndeletePDF' disabledValue='hidden'>"href="<#ACTION action='21' type='11'>&Value=<#TRANSACTION field='TransactionNumber'>" class="menuUndeletePdf">
<span aria-hidden="true" <span class="fa-stack" style="vertical-align: top;">
<span class="fas fa-trash-alt fa-stack-1x"></span>
<span class="fas fa-ban fa-stack-2x text-danger"></span>
</span> Undelete Item
</a>To this:
<a class="btn btn-light menuUndeletePdf <#TRANSACTION field='RequestActionAllowed' name='UndeletePDF' disabledValue='hidden'>"href="<#ACTION action='21' type='11'>&Value=<#TRANSACTION field='TransactionNumber'>">
<span aria-hidden="true" class="fa-stack">
<span class="fas fa-trash-alt fa-stack-1x"></span>
<span class="fas fa-ban fa-stack-2x text-danger"></span>
</span> Undelete Item
</a>Bug# 9309
0 votesReleased in v9.1 web page changes on 11/23/2020
-
Blocked user status line styling is inconsistent
The default blocked user page needs to be updated to consistently look like other pages.
Bug# 7682
0 votesReleased in v9.1 web page changes on 11/23/2020
-
Drop-downs missing options in the web pages
Some drop-downs in the ILLiad default pages are missing options.
Workaround - To add these options back into the default pages change this:
<select id="AcceptAlternateEdition" name="AcceptAlternateEdition" size="1" class="custom-select mr-sm-2">
<option selected><#PARAM name='AcceptAlternateEdition'></option
<option>No</option>
</select>To this:
<select id="AcceptAlternateEdition" name="AcceptAlternateEdition" size="1" class="custom-select mr-sm-2" data-persistedValue="<#PARAM name='AcceptAlternateEdition'>">
<option>Yes</option>
<option>No</option>
</select>Bug# 9383
0 votesReleased in v9.1 web page changes on 11/23/2020
-
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) responded
Released in ILLiad v9.1 default web pages on August 31st, 2021.
-
DLL shows incorrect date/time on transaction notes
The date shows up correctly in the client and the database but not in the transaction notes.
v9.1
Bug# 78470 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in ILLiad 9.2
-
Adding new lines to the web alerts breaks the alert
When adding carriage returns, it breaks the JSON parse.
Workaround: Use a <br> tag before starting a new line to ensure the alert will display properly.
v9.1
Bug# 71720 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in ILLiad 9.2