Canvas Updates
From e-Learning Documentation
Line 1: | Line 1: | ||
- | Production Release Notes for Saturday, | + | Production Release Notes for Saturday, April 4, 2015 |
+ | <h3><strong>Upcoming Canvas Changes</strong></h3> | ||
+ | <p>On <strong>June 6, 2015</strong>, the following changes will be made in Canvas:</p> | ||
+ | <ul> | ||
+ | <li> Differentiated Assignments (by section) will no longer be a Feature Option in Canvas and will be enabled for all Canvas users as a standard feature. Learn more about Differentiated Assignments as an [http://guides.instructure.com/s/2204/m/4152/l/196631-what-feature-options-are-currently-available-for-my-canvas-course instructor].</li> | ||
+ | <li> The new Files interface (Better File Browsing) will no longer be a Feature Option in Canvas and will be enabled for all Canvas users as a standard feature. This change will enable New Files on the course and user levels. Learn more about New Files as an [http://guides.instructure.com/s/2204/m/4152/l/196631-what-feature-options-are-currently-available-for-my-canvas-course instructor].</li> | ||
+ | </ul> | ||
<h1>New Features</h1> | <h1>New Features</h1> | ||
- | <h2> | + | <h2>Outcomes</h2> |
- | <h3> | + | <h3>Calculation Methods</h3> |
- | <p> | + | <p><em>This feature is used in conjunction with the [http://guides.instructure.com/m/4152/l/196631-what-feature-options-are-currently-available-for-my-canvas-course Learning Mastery Gradebook] course feature option. </em></p> |
- | <p></p> | + | <p>Outcomes allows instructors and admins to specify one of four calculation methods used for student mastery in the Learning Mastery Gradebook and Student Learning Mastery Gradebook. Previously the only calculation method available in Canvas was calculating by highest score.</p> |
- | < | + | <p>When viewing Outcomes at the Account, Subaccount, and Course levels, the current calculation method displays as part of the outcome data.</p> |
- | <p> | + | <p> </p> |
- | <p></p> | + | <p><strong>Decaying Average</strong>: Calculate the average of all aligned items while weighing the most recent item at a higher percentage. Traditional averaging weighs all assessments equally and does not consider the student’s current understanding, but this calculation assesses the current attempt while still recognizing prior attempts, which helps display trends in student learning. Ultimately, the overall score reflects the current level of understanding instead of the average of learning over time.</p> |
- | + | <p>By default, the decaying average is set at 65/35, meaning the current item is weighted at 65%, and the average of all other user scores is weighted at 35%. However, users can specify between 1% and 99% for the current percentage, and prior scores are weighted against the percentage difference. Note that the average is rounded to the next two decimals.</p> | |
- | < | + | <p>For example, a student has four aligned items with scores of 4, 3, 2, and 5. If the current item is set to be weighted at 75% of mastery, prior scores are weighted at 25%:</p> |
- | < | + | <ul> |
- | <p> | + | <li> Current item score: 5 </li> |
- | <p> | + | <li> Average of prior item scores: (4 + 3 + 2) / 3 = 3 </li> |
- | <p></p> | + | <li> Calculated score: 5 (.75) + 3 (.25) = 3.75 + .75 = 4.5 </li> |
- | + | </ul> | |
- | < | + | <p> </p> |
- | < | + | <p><strong>n Number of Times</strong>: Require a specific number of times mastery must be met or exceeded and the number of aligned items that must be completed for calculation eligibility. Any scores that do not meet mastery are not part of the calculation.</p> |
- | <p> | + | <p>By default, the item requirement is set at 2. However, users can specify between 2 and 5 items required for mastery.</p> |
+ | <p>For example, a student is required to achieve mastery 2 times with a mastery score of 5. If the student has scores of 1, 3, 2, 4, 5, 3, and 6, only the scores of 5 and 6 would be part of the calculation.</p> | ||
+ | <ul> | ||
+ | <li> Average score of eligible items: 5 + 6 = 11</li> | ||
+ | <li> Calculated score: 11 / 2 = 5.5</li> | ||
+ | </ul> | ||
+ | <p> </p> | ||
+ | <p><strong>Most Recent Score</strong>: Always use the score in the most recent item.</p> | ||
+ | <p> </p> | ||
+ | <p><strong>Highest Score</strong>: Always use the highest score in all attempts.</p> | ||
+ | <p> </p> | ||
+ | <p><em>Notes:<br></em></p> | ||
+ | <p>For all existing Outcomes in Canvas, the default calculation is the highest score. Unless an outcome has not yet been used to assess a student, existing outcomes cannot be edited and must be re-created to apply another calculation method.</p> | ||
+ | <p>For new Outcomes created in the Canvas interface, the default calculation is Decaying Average.</p> | ||
+ | <p> </p> | ||
+ | <h3>Gradebook Display</h3> | ||
+ | <p>Assessment scores display in the Learning Mastery Gradebook for each outcome according to the calculation method. Additionally, instructors can view the current calculation method as part of the Outcomes overview window.</p> | ||
+ | <p> </p> | ||
<h1>Updated Features</h1> | <h1>Updated Features</h1> | ||
- | + | <h2>Gradebook</h2> | |
- | <h2> | + | <h3>Unpublished Courses and Grades</h3> |
- | <h3> | + | <p>Instructors can edit the Gradebook while a course is unpublished. This feature reverts behavior that was previously adjusted in the March 14 release.</p> |
- | <p> | + | <p> </p> |
- | <p></p> | + | <h2>Learning Mastery Gradebook</h2> |
- | + | <h3>Mastery Levels</h3> | |
+ | <p><em>This feature is used in conjunction with the [http://guides.instructure.com/m/4152/l/196631-what-feature-options-are-currently-available-for-my-canvas-course Learning Mastery Gradebook] course feature option. </em></p> | ||
+ | <p>In the Learning Mastery Gradebook, the Gradebook includes an <strong>Exceeds Mastery</strong> level, which is a score earned above the mastery threshold. Additionally, the Remedial level has been renamed to <strong>Well Below Mastery</strong>.</p> | ||
+ | <p> </p> | ||
+ | <h2>Rich Content Editor</h2> | ||
+ | <h3>Interface Update</h3> | ||
+ | <p>The Rich Content Editor has been updated with the most recent interface design and ultimately update provides more backend functionality to support future upgrades to the Rich Content Editor.</p> | ||
+ | <p>The main feature of this upgrade includes better support for creating and deleting tables. Users can easily add, merge, and split table cells without having to switch to the HTML Editor. Rows can be added, copied, and pasted anywhere in the table.</p> | ||
+ | <p>The editor also supports directional text so users can insert content right to left. This feature can be added using the Right to Left button within the editor.</p> | ||
+ | <p>Beneath the Rich Content Editor window, users can view HTML elements for any selected content. This feature is beneficial for users who work with HTML and want to view or confirm placement of content.</p> | ||
+ | <p> </p> | ||
+ | <h1>Other Updates</h1> | ||
+ | <h2>Analytics</h2> | ||
+ | <h3>Student Submissions</h3> | ||
+ | <p>For student analytics, the <em>Assignments</em> analytics section has been renamed to <em>Submissions</em>. Additionally, no icons are displayed for assignments that do not include a submission (i.e. not graded, on paper) or for assignments that do not apply to a student because of differentiated assignments. These changes were made because assignments that did not require a submission were always being shown as missing, and Canvas could not calculate whether or not a non-submission assignment was submitted on time.</p> | ||
+ | <h2>Conferences</h2> | ||
+ | <h3>Enable Recording Button</h3> | ||
+ | <p>When users create a conference, the checkbox to record a conference has been renamed to Enable recording for this conference. Some users were unaware that the actual recording button is within the Conferences interface and that marking the checkbox did not automatically record the conference. This change helps clarify the purpose of the checkbox, which simply enables the recording tools within the Conferences interface. Functionality for this feature is not affected.</p> | ||
+ | <p> </p> | ||
+ | <h2>Discussions</h2> | ||
+ | <h3>Discussion Creation Dates</h3> | ||
+ | <p>Discussion creation dates have been modified as an instructor permission, meaning the student and observer views do not display the creation date for a discussion.</p> | ||
+ | <p>This change helps instructors copy course content without having to modify any Discussions content; only instructors can view the creation date for a discussion.</p> | ||
+ | <p>Additionally, when Discussions are copied in a course, the last post date will not display on the Discussions index page; the last post date was displaying as the creation date of the discussion. This feature is not currently in available for testing in beta but will be part of Saturday’s release.</p> | ||
+ | <p> </p> | ||
<h2>Student Learning Mastery Gradebook</h2> | <h2>Student Learning Mastery Gradebook</h2> | ||
- | <h3> | + | <h3>Mastery Count Indicator</h3> |
- | <p> | + | <p>Mastery Count Indicators are used in conjunction with the [http://guides.instructure.com/m/4152/l/196631-what-feature-options-are-currently-available-for-my-canvas-course Student Learning Mastery Gradebook] course feature option.</p> |
- | + | <p>When viewing the Student Learning Mastery Gradebook, students see the outcome group and the number of associated outcomes. On the right side, the total number of outcomes are shown in gray; the left side shows the number of outcomes the student has mastered. The mastery count for the student now does not turn green until the student has started mastering outcomes in the group.</p> | |
- | + | <p> </p> | |
- | + | ||
- | <p></p> | + | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
<h1>Fixed Bugs</h1> | <h1>Fixed Bugs</h1> | ||
<h2>Accessibility</h2> | <h2>Accessibility</h2> | ||
+ | <h3>General</h3> | ||
+ | <p>Focus styles are now included in button states, buttons, tabs, and item groups in both the high contrast mode and default Canvas interface.</p> | ||
<h3>Announcements</h3> | <h3>Announcements</h3> | ||
- | <p> | + | <p>The Announcements Settings Menu is labeled as a button for screen readers.</p> |
- | + | <p>Keyboard users can collapse an individual reply to an announcement.</p> | |
- | < | + | <p>When a keyboard user tries to attach a file to an announcement, focus remains on the Choose File button.</p> |
- | <p> | + | <p>The reply field for announcements displays the info icon next to the Rich Content Editor.</p> |
- | <p> | + | <p>All Announcements elements on the index page are highlighted from left to right.</p> |
- | <p> | + | <p>All announcement reply element buttons are highlighted from left to right.</p> |
- | + | <p>When a keyboard user accesses the Settings menu and chooses a command, focus returns to the Settings menu.</p> | |
- | <h3> | + | <h3>Course Settings</h3> |
- | <p> | + | <p>In Course Details, the Description label includes a for attribute to indicate a course public description.</p> |
- | + | <h3>Course Setup Checklist</h3> | |
+ | <p>The Course Setup Checklist includes a screen reader message indicating when the checklist items are complete or incomplete.</p> | ||
+ | <h3>Conversations</h3> | ||
+ | <p>The People selection menu in Conversations displays a color contrast of 3:1 for the default Canvas interface and 4.5:1 for high contrast profiles.</p> | ||
<h3>Discussions</h3> | <h3>Discussions</h3> | ||
- | <p> | + | <p>The Discussions Settings Menu is labeled as a button for screen readers.</p> |
- | <p> | + | <p>Keyboard users can collapse an individual reply to a discussion.</p> |
- | + | <p>Keyboard users can add and show rubrics for discussions.</p> | |
+ | <p>When a keyboard user tries to attach a file to a discussion, focus remains on the Choose File button.</p> | ||
+ | <p>Each reply field for discussions display an info icon next to the Ri</p> | ||
+ | <p>All Discussions elements are highlighted from left to right.<</p> | ||
+ | <h3>External Apps</h3> | ||
+ | <p>The View App Center and View App Configurations buttons are highligh</p> | ||
<h3>Files</h3> | <h3>Files</h3> | ||
- | <p> | + | <p>In New Files, users can identify and modify the current access restr</p> |
- | <p>The | + | <p>The Settings label has been changed to actions.</p> |
- | + | <p>When closing a file preview, Files retains focus on the name of the file that was being previewed.</p> | |
- | < | + | <p>When a keyboard user attempts to rename a file but cancels the action, focus returns to the file’s name.</p> |
- | <p> | + | <p>Keyboard users can view the file’s information in the preview window.</p> |
- | + | <h3>Modules</h3> | |
- | <h3> | + | <p>All items in the Modules Setting menu retain focus on the menu. When a module item is deleted, focus returns to the previous item; if the previous item was the last item in the module, focus moves to the Module’s settings menu. </p> |
- | <p> | + | <p>When closing the Modules edit window, Modules retains focus on the Settings menu.</p> |
- | + | <p>When keyboard users view the Add Module button, focus is set to the first drag handle in the Module.</p> | |
- | <h3> | + | <h3>Outcomes</h3> |
- | <p> | + | <p>Keyboard users can access the Outcomes Edit menu to open and edit criterion.</p> |
- | <p> | + | <h3>Rich Content Editor</h3> |
- | <p> | + | <p>All shortcuts are correct in the keyboard dialog; users can open the dialog by clicking alt-F8. The information icon also includes hover text to open the help menu.</p> |
- | + | <h3>Rubrics</h3> | |
+ | <p>Keyboard users can delete a rubric. Focus is set to the view longer description link of the previous row. If there is no previous row, focus moves to the title input field.</p> | ||
+ | <p> </p> | ||
+ | <h2>Analytics</h2> | ||
+ | <h3>Course Analytics for Missing Assignments</h3> | ||
+ | <p>Student analytics are not displayed for assignments that do not include a submission (i.e. not graded, on paper).</p> | ||
+ | <p><em>Explanation</em>: Assignment types set to Not Graded were displayed as missing in Course Analytics. This behavior occurred because analytics was not coded to support Not Graded assignments and was also affected by differentiated assignments. Canvas code has been updated to remove submission icons for any assignments that do not include a submission or assignments that do not apply to a student because of differentiated assignments.</p> | ||
+ | <p> </p> | ||
<h2>Announcements</h2> | <h2>Announcements</h2> | ||
- | <h3> | + | <h3>Podcast Link</h3> |
- | <p> | + | <p>Users can access announcement podcasts if an announcement includes a video file.</p> |
- | <p><em>Explanation</em>: | + | <p><em>Explanation</em>: The Announcements podcast link broke when instructors added a video file to an announcement from the content selector. This behavior occurred because of a conflict in media definitions for each media type. Canvas code has been updated to leave out media objects if a media attachment is included as a reply.</p> |
- | + | <h3>Announcements and Course Activity</h3> | |
- | + | <p>Disabling comments in Announcements does not affect course settings and activity logs.</p> | |
- | + | <p><em>Explanation</em>: When an instructor disabled comments in Announcements, either through the Announcements Settings menu or the Course Settings page, the course activity log generated a report that the comments setting had been turned off. This behavior occurred because of changes to course public visibility settings. Canvas code has been updated confirm changes to course settings before updating activity logs.</p> | |
- | + | <p> </p> | |
- | + | ||
- | <h3> | + | |
- | <p> | + | |
- | <p><em>Explanation</em>: When | + | |
- | + | ||
- | + | ||
- | <p> | + | |
- | + | ||
- | + | ||
<h2>Assignments</h2> | <h2>Assignments</h2> | ||
- | <h3> | + | <h3>Differentiated Assignments and Gradebook Uploads</h3> |
- | <p> | + | <p>When Differentiated Assignments is enabled, Gradebook CSV uploads update new assignments and scores.</p> |
- | <p><em>Explanation</em>: | + | <p><em>Explanation</em>: The Differentiated Assignments feature option was conflicting with Gradebook CSV uploads; the upload recognized the assignment but would not update any student scores. Two uploads were required for the same CSV file before the grades would appear. This behavior occurred because the Gradebook was verifying scores for visible assignments, but with Differentiated Assignments, but some students were not required to complete the assignment. Canvas code has been updated to have CSV files verify if the assignment is visible to the student and ignore any student submissions that are not visible.</p> |
- | + | <h3>Assignments and External Tools</h3> | |
- | <h3> | + | <p>Clicking the Enter key in an assignment field does not launch the configure external tool window.</p> |
- | <p> | + | <p><em>Explanation</em>: When a user clicked the Enter (or Return) key in an assignments field, such as points, name, or automatic peer reviews, the assignment launched the configure external tool window. This behavior occurred because the class for the assignment fields was not defined as being for screen readers only. Canvas code has been updated with a clarified button class for screen readers. </p> |
- | <p><em>Explanation</em>: | + | <h3>Assignment Groups</h3> |
- | + | <p>When adding a new assignment to an assignment group, the group retains any assignments added via drag-and-drop functionality.</p> | |
- | <h3> | + | <p><em>Explanation</em>: The drag-and-drop functionality in Assignments was causing existing assignments to disappear from the group until the page was refreshed. When an instructor created a new assignment group and then dragged an existing assignment to the group, adding a new assignment directly in the group caused the existing assignment to disappear. This behavior occurred because of an empty attribute value in the page display for drag-and-drop functionality. Canvas code has been updated to render a refresh to properly recognize drag-and-drop assignments.</p> |
- | <p> | + | <p> </p> |
- | <p><em>Explanation</em>: | + | <h2>Calendar</h2> |
- | + | <h3>Undated Events</h3> | |
- | <h3> | + | <p>Canvas users can create undated events in the Calendar.</p> |
- | <p> | + | <p><em>Explanation</em>: Canvas users were not able to create an undated event in the Calendar. If a user removed the date, upon saving, the event auto-populated with the current date. This behavior occurred because the Calendar was not supporting undated fields. Canvas code has been updated to allow blank date fields and place the undated event in the Undated items list in the sidebar.</p> |
- | <p><em>Explanation</em>: | + | <h3>Syllabus and Media Comments</h3> |
- | + | <p>Users can load the course syllabus and calendar if a media comment exists in a Calendar event with varied due dates.</p> | |
+ | <p><em>Explanation</em>: Course users were unable to load the course syllabus and calendar when a calendar event with varied due dates included a media comment. This behavior occurred because event descriptions were not defined for the course. Canvas code has been updated to verify course context and allow media comments in varied due date event descriptions.</p> | ||
+ | <h3>Calendar Assignment View</h3> | ||
+ | <p>Users can view all content for an assignment in the Calendar.</p> | ||
+ | <p><em>Explanation</em>: Assignments with very long descriptions were not scrollable in the calendar event window. The window pane continued beyond the dimensions of the window instead of stopping at a maximum height. This behavior occurred because the calendar was not defined with a maximum height. Canvas code has been updated to specify the maximum height and width on Calendar event windows as 160 px and 495 px.</p> | ||
+ | <h3>Assignments and Saturday Due Date</h3> | ||
+ | <p>In the Calendar, Assignments dragged to Saturday that are due on or after 11:31 pm post as a Saturday assignment.</p> | ||
+ | <p><em>Explanation</em>: Assignments that were due on or after 11:31pm were not posting correctly when a user dragged and dropped the assignment to a Saturday. The assignment became grayed out and posted on Sunday. This behavior occurred because Canvas was enforcing a 30-minute window for calendar events, which adjusted assignments created after 11:31 pm to midnight (and wrapped the assignment to Sunday). Canvas code has been updated to only enforce the minimum 30-minute duration if the assignment is not due between 11:31 pm and 12:00 am.</p> | ||
+ | <h3>Section Limits and Scheduler</h3> | ||
+ | <p>Section-limited instructors can see course sections in Scheduler.</p> | ||
+ | <p><em>Explanation</em>: Instructors who could only view specific sections of a course were not able to view the course in Scheduler. This behavior occurred because the Calendar was confirming the appointment group permission as all-or-nothing course functionality. Canvas code has been updated to confirm the appointment group permission while distinguishing between sections in the course.</p> | ||
+ | <p> </p> | ||
+ | <h2>Collaborations</h2> | ||
+ | <h3>Group Collaborations</h3> | ||
+ | <p>Instructors can create group collaborations without being a member of the group.</p> | ||
+ | <p><em>Explanation</em>: Instructors were not able to create a group collaboration without being a member of the group. Additionally, all user groups were being shown to the collaboration creator, even if the group was not part of the course. This behavior occurred because the groups permission was not verifying the user, both for creating collaborations and listing groups. Canvas code has been updated to confirm the manage groups permission for instructors and only show relevant groups for the course.</p> | ||
+ | <p> </p> | ||
+ | <h2>Conferences</h2> | ||
+ | <h3>Long-Running Conferences and End Now Dashboard Button</h3> | ||
+ | <p>Users can end a long-running conference from the Course Dashboard.</p> | ||
+ | <p><em>Explanation</em>: When a user had access to create a long-running (no time limit) conference, the activity stream on the course dashboard included a button to join or end the conference. Clicking the End Now button displayed a page of code content. This behavior occurred because the End Now button was not properly configured to close the conference. Canvas code has been updated to confirm closing the conference and includes a confirmation message. </p> | ||
+ | <p> </p> | ||
<h2>Conversations</h2> | <h2>Conversations</h2> | ||
- | <h3> | + | <h3>Conversation Filters</h3> |
- | <p> | + | <p>Conversations can be filtered by course if a student and instructor share more than one course.</p> |
- | <p><em>Explanation</em>: When | + | <p><em>Explanation</em>: When filtering Conversations by course, when a student and instructor had more shared more than one course, the messages were all filtered into the course with the lower ID number and were not visible as part of the other course. This behavior occurred because the updated time was not preloaded as part of the filter context, pulling older conversations that were no longer relevant. Canvas code has been updated to include updated tags as part of conversations context. </p> |
- | + | <h3>Group Conversations</h3> | |
+ | <p>Group lists load quickly in the Conversation drop-down menu.</p> | ||
+ | <p><em>Explanation</em>: When a user tried to view a group list in Conversations, the list of users was delayed in loading. This behavior occurred because all contexts were being loaded for the group recipients. Canvas code has been updated to refactor group user lists and load only relevant context. </p> | ||
+ | <p> </p> | ||
<h2>Course Imports</h2> | <h2>Course Imports</h2> | ||
- | <h3> | + | <h3>Essay and File Upload Duplication</h3> |
- | <p> | + | <p>Essay questions and File Upload questions are not duplicated as part of a course copy.</p> |
- | <p><em>Explanation</em>: When a | + | <p><em>Explanation</em>: When a quiz is copied into a course twice, and select content is selected in one of the copy types, Essay and File Upload questions were duplicating in the course. This behavior occurred because of an error with quiz question migration IDs. Canvas code has been updated to retain and verify quiz question IDs for course imports.</p> |
- | + | <h3>Syllabus Public Setting</h3> | |
- | <h3> | + | <p>Syllabi that are public on course copy are retained as public.</p> |
- | <p> | + | <p><em>Explanation</em>: When an instructor enabled the Make the syllabus for this course publicly visible option and copied the course, the syllabus option was not applied as part of the import. This behavior occurred because the public syllabus was not defined as a clonable attribute for course copies. Canvas code has been updated to preserve the public syllabus attribute and compare the settings when copying a course.</p> |
- | <p><em>Explanation</em>: | + | <h3>Moodle and Graded Discussions</h3> |
- | + | <p>Point values and graded options in Moodle advanced forums are imported to Graded Discussions.</p> | |
+ | <p><em>Explanation</em>: When a Moodle file was imported that contained advanced forums (graded discussions), the point value and graded options were not retained. This behavior occurred because Canvas required a more current code element to support Moodle files. Canvas code has been updated to include a more recent Moodle dependency.</p> | ||
+ | <h3>Ungraded Discussions and Until Date</h3> | ||
+ | <p>Ungraded Discussions retain the Until Date as part of course copies.</p> | ||
+ | <p><em>Explanation</em>: Course copies were not retaining Until Dates in ungraded discussions, and users were required to adjust the dates manually when the copy had concluded. This behavior occurred because the Until (lock) date was not included as a migration element. Canvas code has been updated to add the lock date as part of course copies. </p> | ||
+ | <h3>Blackboard Matching Questions</h3> | ||
+ | <p>Matching questions in Blackboard are imported into Canvas quizzes.</p> | ||
+ | <p><em>Explanation</em>: When a Blackboard file was imported that contained matching questions in a quiz, the quiz displayed an error for the quiz. This behavior occurred because of an error when referencing quiz answer IDs. Canvas code has been updated to ensure the question IDs reference the correct quiz response.</p> | ||
+ | <h3>Assignment Group Settings</h3> | ||
+ | <p>When copying individual assignments, course copies do not associate updated information from the source course’s assignment group.</p> | ||
+ | <p><em>Explanation</em>: When copying an individual assignment from a course that is part of an assignment group, instructors encountered a variety of error types. The new course applied rules to drop the lowest grade, even when no rule was set previously, and if the course copy included an assignment group with a changed name, the name would also update in the former course. This behavior occurred because of a change in course copy procedure in a previous release. Canvas code has been updated to copy individual assignments if the group where they were originally copied does not already exist in the destination course.</p> | ||
+ | <p> </p> | ||
<h2>Course Settings</h2> | <h2>Course Settings</h2> | ||
- | <h3> | + | <h3>Instructors and Concluded Enrollments</h3> |
- | <p> | + | <p>When a course is concluded, instructors can still view all Course Navigation links.</p> |
- | <p><em>Explanation</em>: When a | + | <p><em>Explanation</em>: When a course was concluded by Term Dates, instructors could only view navigation items and files/folders available to students. If the instructor hid any Course Navigation links from students, those links were also not able to be viewed after their Term access ended unless the dates were overridden by course dates. This behavior occurred because the course was not verifying enrollment types for instructors. Canvas code has been updated to confirm enrollments within the course and not hide Course Navigation tabs for instructors.</p> |
- | + | <h3>External Apps</h3> | |
- | + | <p>Users can view the External Apps tab and add new apps in Course Settings.</p> | |
- | <h3> | + | <p><em>Explanation</em>: The External Apps tab generated multiple behaviors within Course Settings. If a user opened Course Settings and the last open tab was External Apps, the apps tab would not load. When viewing an app, if a user repeatedly clicked the Save button when adding an app, multiple app entries were created. Leaving a secret field blank overwrote the external tool with a blank secret. And the external tool configuration screen domain would not display in the Canvas interface. These behaviors occurred because of recent changes made to the External Tools App. Canvas code has been updated to correct necessary configurations and app values</p> |
- | <p> | + | <p> </p> |
- | <p><em>Explanation</em>: | + | <h2>Dashboard</h2> |
- | + | <h3>Coming Up Section</h3> | |
- | + | <p>The Coming Up section of the Course or User Dashboard indicates the correct time.</p> | |
- | <p> | + | <p><em>Explanation</em>: When they are more available items in the Coming Up section of the Course or User Dashboard sidebar, the link to display more items showed as more in the past week instead of more in the next week. This behavior occurred because the logic was being copied from the Recent Feedback section, which showed the past 2 weeks. Canvas code has been updated to display the correct time adjective.</p> |
- | < | + | <p> </p> |
- | + | ||
- | <h3>Section | + | |
- | <p> | + | |
- | <p><em>Explanation</em>: When | + | |
- | + | ||
<h2>Discussions</h2> | <h2>Discussions</h2> | ||
- | <h3> | + | <h3>No Title Discussions and TurnitIn IDs</h3> |
- | <p> | + | <p>Discussions are not created for a course except through direct activity from a user.</p> |
- | <p><em>Explanation</em>: | + | <p><em>Explanation</em>: Some courses were generating discussions with no titles and no attached users. This behavior occurred in courses with enabled TurnitIn accounts, whose IDs were generating discussions for the course. Canvas code has been updated to only generate assignments via TurnItIn when applicable to the course.</p> |
- | + | <h3>Disappearing Discussion Comments</h3> | |
- | <h3> | + | <p>Editing a discussion reply retains all associated discussion comments.</p> |
- | <p> | + | <p><em>Explanation</em>: When a discussion reply was edited, all associated comments as part of the thread would disappear in the discussion topic. This behavior affected both threaded and unthreaded discussions and occurred because of a reply capture error. The reply held an instance of the parent attribute, as opposed to just referencing the parent, so the replies were removed when the associated reply was edited. Canvas code has been updated to track and retain replies after the API edit request is complete.</p> |
- | <p><em>Explanation</em>: | + | <h3>Group Discussion Attachments</h3> |
- | + | <p>Attachments in group discussions are viewable to all group members.</p> | |
- | + | <p><em>Explanation</em>: When a user attached a file to a discussion topic as part of a group discussion, the attachment was not viewable to the rest of the group. This behavior occurred because the group attachment ID was not a proper group attribute. Canvas code has been updated to mirror behavior in course groups by defining the group attachment ID and copying all appropriate attributes from the parent discussion.</p> | |
- | + | <h3>Podcast Link</h3> | |
- | + | <p>Users can access discussion podcasts if a discussion includes a video file.</p> | |
- | + | <p><em>Explanation</em>: The Discussions podcast link broke when instructors added a video file to a discussion from the content selector. This behavior occurred because of a conflict in media definitions for each media type. Canvas code has been updated to leave out media objects if a media attachment is included as a reply.</p> | |
- | <h3>Group Discussion | + | <p> </p> |
- | <p> | + | |
- | <p><em>Explanation</em>: When | + | |
- | + | ||
- | <h3> | + | |
- | <p> | + | |
- | <p><em>Explanation</em>: | + | |
- | + | ||
<h2>ePortfolios</h2> | <h2>ePortfolios</h2> | ||
- | <h3> | + | <h3>Last Updated Timestamp</h3> |
- | <p> | + | <p>ePortfolios display the time of the last update.</p> |
- | <p><em>Explanation</em>: When a user | + | <p><em>Explanation</em>: When a user updates an ePortfolio, the last updated field (as seen on the ePortfolios dashboard) was not being updated to reflect the most recent time. This behavior occurred because changes were not set to trigger an update. Canvas code has been updated to touch the last updated field when a change is made to an ePortfolio.</p> |
- | + | <p> </p> | |
<h2>Files</h2> | <h2>Files</h2> | ||
- | <h3>Files | + | <h3>Drag and Drop Files List</h3> |
- | <p> | + | <p>When Better File Browsing is enabled, drag-and-drop functionality is enabled for the entire folder window.</p> |
- | <p><em>Explanation</em>: When | + | <p><em>Explanation</em>: When an instructor uses drag and drop to add a file to a course with Better File Browsing enabled, the droppable area was sized only as large as the list of files; empty areas were inactive. This behavior was especially noticeable for mostly empty folders and occurred because the drop space wasn’t expanding to the entire area. Canvas code has been updated with CSS to expand the files upload area.</p> |
- | + | <h3>Fullscreen Video Previews</h3> | |
- | <h3> | + | <p>When Better File Browsing is enabled, videos can be previewed in full screen.</p> |
- | <p> | + | <p><em>Explanation</em>: When a user attempted to preview a video file in full screen, the file disappeared completely but continued playing. This behavior occurred because of a height calculation error in the preview window. Canvas code has been updated to correct the container elements for the preview display.</p> |
- | <p><em>Explanation</em>: When a user | + | <h3>File Upload Previews</h3> |
- | + | <p>When Better File Browsing is enabled, users can preview a file upload directly after uploading the file.</p> | |
+ | <p><em>Explanation</em>: When a user uploaded a file, relevant previews (such as images) did not appear until the page was refreshed. This behavior occurred because of an outdated file in React, a the JavaScript library for building user interfaces in Canvas. Canvas code has been updated with a newer version of React.</p> | ||
+ | <h3>Slash in Files URLs</h3> | ||
+ | <p>When Better File Browsing is enabled, users can load files with a slash in the URL.</p> | ||
+ | <p><em>Explanation</em>: When a files URL included a slash, such as canvas.com/files/, the file would not load. This behavior occurred because of an outdated file in React, a the JavaScript library for building user interfaces in Canvas. Canvas code has been updated with a newer version of React.</p> | ||
+ | <h3>Moving Files and Duplicate Names</h3> | ||
+ | <p>When Better File Browsing is enabled, users are prompted to replace/change the name of a file if it is moved to a location with the same file name.</p> | ||
+ | <p><em>Explanation</em>: When a user moved a file to a folder that had a file with the same name, Files did not create a prompt to change the name or replace the current file. This behavior occurred because prompts were only coded as part of uploading files. Canvas code has been updated to view duplicate file names for moving files.</p> | ||
+ | <p> </p> | ||
<h2>Gradebook</h2> | <h2>Gradebook</h2> | ||
- | <h3> | + | <h3>Grading Schemes</h3> |
- | + | <p>New grading schemes save with the included data.</p> | |
- | + | <p><em>Explanation</em>: When a user created a grading scheme and saved the data, the grading scheme was being overwritten with the default scheme data but only affect the first save of the grading scheme; editing and re-saving the scheme retained all data changes. This behavior occurred because of a misalignment with grading standard IDs. Canvas code has been updated to clarify default data and grading standard IDs. Additionally, users cannot delete a grading scheme row if it is the last remaining row in the grading scheme, and when users save or delete a grading scheme, a confirmation message appears at the top of the window.</p> | |
- | + | <p> </p> | |
- | + | ||
- | <p> | + | |
- | <p><em>Explanation</em>: When | + | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | <p> | + | |
- | + | ||
<h2>Modules</h2> | <h2>Modules</h2> | ||
- | <h3> | + | <h3>Module Menu Files Limit</h3> |
- | <p> | + | <p>When adding a file to a Module, users can choose from all files in the Files list.</p> |
- | <p><em>Explanation</em>: When a | + | <p><em>Explanation</em>: When a user added a file to a Module, some files in root folders were not appearing in the Files list. This behavior occurred because of an inconsistency in the API. Canvas code has been updated to support files as a React component, which is a JavaScript library for building user interfaces in Canvas. This change creates a folder and file store for interacting with the API and ensures that folders that do not contain any files are not shown in the Modules file list.</p> |
- | + | <h3>Group Discussions and Page Completion Requirement</h3> | |
- | <h3> | + | <p>Group discussion module items with the users must contribute to the page requirement show the module progression checkmark when the requirement is complete.</p> |
- | <p> | + | <p><em>Explanation</em>: When a Group Discussion assignment type was included in a module, and users were required to contribute to the group discussion before the assignment could be completed, the module item was not displaying the completed check mark and did not allow the student to progress to the next module item. Users were required to change the assignment type to submit the assignment in order for the permission to apply correctly. This behavior occurred because Modules were not coded to accept completions for course assessments in a group context. Canvas code has been updated to forward group actions to the main course discussion.</p> |
- | <p><em>Explanation</em>: When | + | <h3>Manual Quiz Grades</h3> |
- | + | <p>When an instructor manually grades a quiz that is part of a module progress, students can advance to the next module requirement.</p> | |
- | <h3> | + | <p><em>Explanation</em>: When an instructor manually awarded points to a student for a quiz in the Gradebook, and the quiz was part of a module requirement, the Module did not allow the student to progress to the next module. This behavior occurred from an inconsistency in manual grading; in assignments, students could be rewarded a grade for a non-submitted assignment and accept the grade as a submission. Canvas code has been updated to evaluate quiz module tags and allow for manual grading to unlock quiz module requirements.</p> |
- | <p> | + | <h3>Module Pages and State Changes</h3> |
- | <p><em>Explanation</em>: | + | <p>Modifying the name of a page as well as the state of a page in Modules does not create duplicate pages.</p> |
- | + | <p><em>Explanation</em>: When an instructor added a new page to a module, published the page, changed the name of the page, and unpublished the page, the page was created as a duplicate in the Pages Index page. This behavior occurred because of a misalignment in page IDs. Canvas code has been updated to confirm all page IDs when modifying a page.</p> | |
+ | <p> </p> | ||
<h2>Notifications</h2> | <h2>Notifications</h2> | ||
- | <h3> | + | <h3>Designer Role and Grading Assignments</h3> |
- | <p> | + | <p>Designers do not receive notifications to grade assignments unless they have permission to edit or view grades.</p> |
- | <p><em>Explanation</em>: | + | <p><em>Explanation</em>: In the To Do sidebar of the Course Dashboard, Course Designers were viewing notifications to grade assignments. This behavior occurred because enrollments were only coded as admin and student enrollment types, where Designer was grouped in the admin type. Canvas code has been updated to refactor grading notifications; grading is also specified by instructor and student course IDs to show graded assignments only to instructors.</p> |
- | + | <h3>Groups and Unpublished Courses</h3> | |
- | <h3> | + | <p>Students do not receive notifications for group membership unless the course is published.</p> |
- | <p> | + | <p><em>Explanation</em>: If a student was enrolled in an unpublished course and the instructor assigned the user to a group, the student was receiving a notification about the group membership, allowing the student to access the group before the course was published. This behavior occurred because Canvas was not confirming if the course was available (active) before sending notifications. Canvas code has been updated to not send group membership notifications for unpublished courses.</p> |
- | <p><em>Explanation</em>: | + | <p> </p> |
- | + | ||
<h2>Outcomes</h2> | <h2>Outcomes</h2> | ||
- | <h3> | + | <h3>Prior Outcome Creation Warning</h3> |
- | <p> | + | <p>Users cannot edit outcomes that have been used to assess a student.</p> |
- | <p><em>Explanation</em>: When | + | <p><em>Explanation</em>: When users tried to edit an outcome that had already been used to assess a student, such as modifying the title, description, or point scale, Canvas generated an error message. This behavior occurred because of a change made to the Outcomes API on January 31, 2015, which set the assessment type default value as highest score, and some users wanted to adjust existing outcomes. Canvas does not allow outcomes to be modified if they have already been used to assess a student. Canvas code has been updated to disable the edit button for outcomes that cannot be modified within a course or account.</p> |
- | + | <h3>Account-level Outcomes</h3> | |
- | <h3> | + | <p>Users can view account-level outcomes if they have permission to view the page.</p> |
- | <p> | + | <p><em>Explanation</em>: When a user with permission to view account-level outcomes tried to view an outcome, Canvas generated a page error. This behavior occurred because the outcome was not properly aligning with the account. Canvas code has been updated to update the outcome alignment URL to allow context showing it is an account outcome. This fix was deployed to production on March 26.</p> |
- | <p><em>Explanation</em>: When a | + | <p> </p> |
- | + | <h2>Pages</h2> | |
- | <h3> | + | <h3>Content Selector and Student Pages</h3> |
- | <p> | + | <p>Students can edit course pages if they are given permission in the course.</p> |
- | <p><em>Explanation</em>: When an | + | <p><em>Explanation</em>: When a course allowed students to create pages, students were able to insert a new page from the content selector, but the page could not be saved. This behavior occurred because of an inconsistency with the permission to edit course pages and the account-level permission to manage pages. Canvas code has been updated to confirm permissions to manage pages as part of course page edits.</p> |
+ | <h3>Pages and Periods in Titles</h3> | ||
+ | <p>Pages supports pages with periods in the title.</p> | ||
+ | <p><em>Explanation</em>: When an instructor used the content selector to create a new link to a new page, putting a period in the page title caused a page error. This behavior occurred because periods were not a supported symbol in page titles. Canvas code has been updated to support periods in page titles.</p> | ||
+ | <p> </p> | ||
+ | <h2>Profiles</h2> | ||
+ | <h3>Report Inappropriate Picture Link in Profiles</h3> | ||
+ | <p>The Report Inappropriate Picture link always appears next to a profile picture.</p> | ||
+ | <p><em>Explanation</em>: When profiles were enabled at the account level, the Report Inappropriate Picture link did not appear. However, when Profiles were disabled, the link returned by the listing. This behavior occurred because of an error in the reporting links. Canvas code has been updated to include the Report Inappropriate Picture link for all profile picture listings, no matter if Profiles is enabled for the account.</p> | ||
+ | <h3>Report Inappropriate Picture Link</h3> | ||
+ | <p>Then Report Inappropriate Picture button reports a profile image as reported.</p> | ||
+ | <p><em>Explanation</em>: When a user clicked the Report Inappropriate Pictures button on a user’s profile, the button displayed an error message stating the image was not reported. This behavior occurred because of an error in the action response for the button. Canvas code has been updated to correct the click action and add a confirmation message that the reporting was successful.</p> | ||
+ | <p> </p> | ||
+ | <h2>Rich Content Editor</h2> | ||
+ | <h3>Whitelist Language Tag</h3> | ||
+ | <p>The language tag is retained as a whitelist element in the Rich Content Editor.</p> | ||
+ | <p><em>Explanation</em>: When a user attempted to add an HTML comment, the language tag was being filtered about by the HTML editor. This behavior occurred because of an error in the Canvas whitelist sanitization dependency. Canvas code has been updated to support the language tag in the Canvas whitelist and all HTML elements. </p> | ||
- | |||
- | |||
- | |||
<h1 dir="ltr">Next release schedule: </h1> | <h1 dir="ltr">Next release schedule: </h1> | ||
<ul> | <ul> | ||
<li dir="ltr"> | <li dir="ltr"> | ||
- | <p dir="ltr">Beta release and notes: | + | <p dir="ltr">Beta release and notes: 04/13/15</p> |
</li> | </li> | ||
<li dir="ltr"> | <li dir="ltr"> | ||
- | <p dir="ltr">Production release notes: | + | <p dir="ltr">Production release notes: 04/20/15</p> |
</li> | </li> | ||
<li dir="ltr"> | <li dir="ltr"> | ||
- | <p dir="ltr">Production release and documentation: 04/ | + | <p dir="ltr">Production release and documentation: 04/25/15</p> |
</li> | </li> | ||
</ul> | </ul> |
Revision as of 21:13, 31 March 2015
Production Release Notes for Saturday, April 4, 2015
Upcoming Canvas Changes
On June 6, 2015, the following changes will be made in Canvas:
- Differentiated Assignments (by section) will no longer be a Feature Option in Canvas and will be enabled for all Canvas users as a standard feature. Learn more about Differentiated Assignments as an instructor.
- The new Files interface (Better File Browsing) will no longer be a Feature Option in Canvas and will be enabled for all Canvas users as a standard feature. This change will enable New Files on the course and user levels. Learn more about New Files as an instructor.
New Features
Outcomes
Calculation Methods
This feature is used in conjunction with the Learning Mastery Gradebook course feature option.
Outcomes allows instructors and admins to specify one of four calculation methods used for student mastery in the Learning Mastery Gradebook and Student Learning Mastery Gradebook. Previously the only calculation method available in Canvas was calculating by highest score.
When viewing Outcomes at the Account, Subaccount, and Course levels, the current calculation method displays as part of the outcome data.
Decaying Average: Calculate the average of all aligned items while weighing the most recent item at a higher percentage. Traditional averaging weighs all assessments equally and does not consider the student’s current understanding, but this calculation assesses the current attempt while still recognizing prior attempts, which helps display trends in student learning. Ultimately, the overall score reflects the current level of understanding instead of the average of learning over time.
By default, the decaying average is set at 65/35, meaning the current item is weighted at 65%, and the average of all other user scores is weighted at 35%. However, users can specify between 1% and 99% for the current percentage, and prior scores are weighted against the percentage difference. Note that the average is rounded to the next two decimals.
For example, a student has four aligned items with scores of 4, 3, 2, and 5. If the current item is set to be weighted at 75% of mastery, prior scores are weighted at 25%:
- Current item score: 5
- Average of prior item scores: (4 + 3 + 2) / 3 = 3
- Calculated score: 5 (.75) + 3 (.25) = 3.75 + .75 = 4.5
n Number of Times: Require a specific number of times mastery must be met or exceeded and the number of aligned items that must be completed for calculation eligibility. Any scores that do not meet mastery are not part of the calculation.
By default, the item requirement is set at 2. However, users can specify between 2 and 5 items required for mastery.
For example, a student is required to achieve mastery 2 times with a mastery score of 5. If the student has scores of 1, 3, 2, 4, 5, 3, and 6, only the scores of 5 and 6 would be part of the calculation.
- Average score of eligible items: 5 + 6 = 11
- Calculated score: 11 / 2 = 5.5
Most Recent Score: Always use the score in the most recent item.
Highest Score: Always use the highest score in all attempts.
Notes:
For all existing Outcomes in Canvas, the default calculation is the highest score. Unless an outcome has not yet been used to assess a student, existing outcomes cannot be edited and must be re-created to apply another calculation method.
For new Outcomes created in the Canvas interface, the default calculation is Decaying Average.
Gradebook Display
Assessment scores display in the Learning Mastery Gradebook for each outcome according to the calculation method. Additionally, instructors can view the current calculation method as part of the Outcomes overview window.
Updated Features
Gradebook
Unpublished Courses and Grades
Instructors can edit the Gradebook while a course is unpublished. This feature reverts behavior that was previously adjusted in the March 14 release.
Learning Mastery Gradebook
Mastery Levels
This feature is used in conjunction with the Learning Mastery Gradebook course feature option.
In the Learning Mastery Gradebook, the Gradebook includes an Exceeds Mastery level, which is a score earned above the mastery threshold. Additionally, the Remedial level has been renamed to Well Below Mastery.
Rich Content Editor
Interface Update
The Rich Content Editor has been updated with the most recent interface design and ultimately update provides more backend functionality to support future upgrades to the Rich Content Editor.
The main feature of this upgrade includes better support for creating and deleting tables. Users can easily add, merge, and split table cells without having to switch to the HTML Editor. Rows can be added, copied, and pasted anywhere in the table.
The editor also supports directional text so users can insert content right to left. This feature can be added using the Right to Left button within the editor.
Beneath the Rich Content Editor window, users can view HTML elements for any selected content. This feature is beneficial for users who work with HTML and want to view or confirm placement of content.
Other Updates
Analytics
Student Submissions
For student analytics, the Assignments analytics section has been renamed to Submissions. Additionally, no icons are displayed for assignments that do not include a submission (i.e. not graded, on paper) or for assignments that do not apply to a student because of differentiated assignments. These changes were made because assignments that did not require a submission were always being shown as missing, and Canvas could not calculate whether or not a non-submission assignment was submitted on time.
Conferences
Enable Recording Button
When users create a conference, the checkbox to record a conference has been renamed to Enable recording for this conference. Some users were unaware that the actual recording button is within the Conferences interface and that marking the checkbox did not automatically record the conference. This change helps clarify the purpose of the checkbox, which simply enables the recording tools within the Conferences interface. Functionality for this feature is not affected.
Discussions
Discussion Creation Dates
Discussion creation dates have been modified as an instructor permission, meaning the student and observer views do not display the creation date for a discussion.
This change helps instructors copy course content without having to modify any Discussions content; only instructors can view the creation date for a discussion.
Additionally, when Discussions are copied in a course, the last post date will not display on the Discussions index page; the last post date was displaying as the creation date of the discussion. This feature is not currently in available for testing in beta but will be part of Saturday’s release.
Student Learning Mastery Gradebook
Mastery Count Indicator
Mastery Count Indicators are used in conjunction with the Student Learning Mastery Gradebook course feature option.
When viewing the Student Learning Mastery Gradebook, students see the outcome group and the number of associated outcomes. On the right side, the total number of outcomes are shown in gray; the left side shows the number of outcomes the student has mastered. The mastery count for the student now does not turn green until the student has started mastering outcomes in the group.
Fixed Bugs
Accessibility
General
Focus styles are now included in button states, buttons, tabs, and item groups in both the high contrast mode and default Canvas interface.
Announcements
The Announcements Settings Menu is labeled as a button for screen readers.
Keyboard users can collapse an individual reply to an announcement.
When a keyboard user tries to attach a file to an announcement, focus remains on the Choose File button.
The reply field for announcements displays the info icon next to the Rich Content Editor.
All Announcements elements on the index page are highlighted from left to right.
All announcement reply element buttons are highlighted from left to right.
When a keyboard user accesses the Settings menu and chooses a command, focus returns to the Settings menu.
Course Settings
In Course Details, the Description label includes a for attribute to indicate a course public description.
Course Setup Checklist
The Course Setup Checklist includes a screen reader message indicating when the checklist items are complete or incomplete.
Conversations
The People selection menu in Conversations displays a color contrast of 3:1 for the default Canvas interface and 4.5:1 for high contrast profiles.
Discussions
The Discussions Settings Menu is labeled as a button for screen readers.
Keyboard users can collapse an individual reply to a discussion.
Keyboard users can add and show rubrics for discussions.
When a keyboard user tries to attach a file to a discussion, focus remains on the Choose File button.
Each reply field for discussions display an info icon next to the Ri
All Discussions elements are highlighted from left to right.<
External Apps
The View App Center and View App Configurations buttons are highligh
Files
In New Files, users can identify and modify the current access restr
The Settings label has been changed to actions.
When closing a file preview, Files retains focus on the name of the file that was being previewed.
When a keyboard user attempts to rename a file but cancels the action, focus returns to the file’s name.
Keyboard users can view the file’s information in the preview window.
Modules
All items in the Modules Setting menu retain focus on the menu. When a module item is deleted, focus returns to the previous item; if the previous item was the last item in the module, focus moves to the Module’s settings menu.
When closing the Modules edit window, Modules retains focus on the Settings menu.
When keyboard users view the Add Module button, focus is set to the first drag handle in the Module.
Outcomes
Keyboard users can access the Outcomes Edit menu to open and edit criterion.
Rich Content Editor
All shortcuts are correct in the keyboard dialog; users can open the dialog by clicking alt-F8. The information icon also includes hover text to open the help menu.
Rubrics
Keyboard users can delete a rubric. Focus is set to the view longer description link of the previous row. If there is no previous row, focus moves to the title input field.
Analytics
Course Analytics for Missing Assignments
Student analytics are not displayed for assignments that do not include a submission (i.e. not graded, on paper).
Explanation: Assignment types set to Not Graded were displayed as missing in Course Analytics. This behavior occurred because analytics was not coded to support Not Graded assignments and was also affected by differentiated assignments. Canvas code has been updated to remove submission icons for any assignments that do not include a submission or assignments that do not apply to a student because of differentiated assignments.
Announcements
Podcast Link
Users can access announcement podcasts if an announcement includes a video file.
Explanation: The Announcements podcast link broke when instructors added a video file to an announcement from the content selector. This behavior occurred because of a conflict in media definitions for each media type. Canvas code has been updated to leave out media objects if a media attachment is included as a reply.
Announcements and Course Activity
Disabling comments in Announcements does not affect course settings and activity logs.
Explanation: When an instructor disabled comments in Announcements, either through the Announcements Settings menu or the Course Settings page, the course activity log generated a report that the comments setting had been turned off. This behavior occurred because of changes to course public visibility settings. Canvas code has been updated confirm changes to course settings before updating activity logs.
Assignments
Differentiated Assignments and Gradebook Uploads
When Differentiated Assignments is enabled, Gradebook CSV uploads update new assignments and scores.
Explanation: The Differentiated Assignments feature option was conflicting with Gradebook CSV uploads; the upload recognized the assignment but would not update any student scores. Two uploads were required for the same CSV file before the grades would appear. This behavior occurred because the Gradebook was verifying scores for visible assignments, but with Differentiated Assignments, but some students were not required to complete the assignment. Canvas code has been updated to have CSV files verify if the assignment is visible to the student and ignore any student submissions that are not visible.
Assignments and External Tools
Clicking the Enter key in an assignment field does not launch the configure external tool window.
Explanation: When a user clicked the Enter (or Return) key in an assignments field, such as points, name, or automatic peer reviews, the assignment launched the configure external tool window. This behavior occurred because the class for the assignment fields was not defined as being for screen readers only. Canvas code has been updated with a clarified button class for screen readers.
Assignment Groups
When adding a new assignment to an assignment group, the group retains any assignments added via drag-and-drop functionality.
Explanation: The drag-and-drop functionality in Assignments was causing existing assignments to disappear from the group until the page was refreshed. When an instructor created a new assignment group and then dragged an existing assignment to the group, adding a new assignment directly in the group caused the existing assignment to disappear. This behavior occurred because of an empty attribute value in the page display for drag-and-drop functionality. Canvas code has been updated to render a refresh to properly recognize drag-and-drop assignments.
Calendar
Undated Events
Canvas users can create undated events in the Calendar.
Explanation: Canvas users were not able to create an undated event in the Calendar. If a user removed the date, upon saving, the event auto-populated with the current date. This behavior occurred because the Calendar was not supporting undated fields. Canvas code has been updated to allow blank date fields and place the undated event in the Undated items list in the sidebar.
Syllabus and Media Comments
Users can load the course syllabus and calendar if a media comment exists in a Calendar event with varied due dates.
Explanation: Course users were unable to load the course syllabus and calendar when a calendar event with varied due dates included a media comment. This behavior occurred because event descriptions were not defined for the course. Canvas code has been updated to verify course context and allow media comments in varied due date event descriptions.
Calendar Assignment View
Users can view all content for an assignment in the Calendar.
Explanation: Assignments with very long descriptions were not scrollable in the calendar event window. The window pane continued beyond the dimensions of the window instead of stopping at a maximum height. This behavior occurred because the calendar was not defined with a maximum height. Canvas code has been updated to specify the maximum height and width on Calendar event windows as 160 px and 495 px.
Assignments and Saturday Due Date
In the Calendar, Assignments dragged to Saturday that are due on or after 11:31 pm post as a Saturday assignment.
Explanation: Assignments that were due on or after 11:31pm were not posting correctly when a user dragged and dropped the assignment to a Saturday. The assignment became grayed out and posted on Sunday. This behavior occurred because Canvas was enforcing a 30-minute window for calendar events, which adjusted assignments created after 11:31 pm to midnight (and wrapped the assignment to Sunday). Canvas code has been updated to only enforce the minimum 30-minute duration if the assignment is not due between 11:31 pm and 12:00 am.
Section Limits and Scheduler
Section-limited instructors can see course sections in Scheduler.
Explanation: Instructors who could only view specific sections of a course were not able to view the course in Scheduler. This behavior occurred because the Calendar was confirming the appointment group permission as all-or-nothing course functionality. Canvas code has been updated to confirm the appointment group permission while distinguishing between sections in the course.
Collaborations
Group Collaborations
Instructors can create group collaborations without being a member of the group.
Explanation: Instructors were not able to create a group collaboration without being a member of the group. Additionally, all user groups were being shown to the collaboration creator, even if the group was not part of the course. This behavior occurred because the groups permission was not verifying the user, both for creating collaborations and listing groups. Canvas code has been updated to confirm the manage groups permission for instructors and only show relevant groups for the course.
Conferences
Long-Running Conferences and End Now Dashboard Button
Users can end a long-running conference from the Course Dashboard.
Explanation: When a user had access to create a long-running (no time limit) conference, the activity stream on the course dashboard included a button to join or end the conference. Clicking the End Now button displayed a page of code content. This behavior occurred because the End Now button was not properly configured to close the conference. Canvas code has been updated to confirm closing the conference and includes a confirmation message.
Conversations
Conversation Filters
Conversations can be filtered by course if a student and instructor share more than one course.
Explanation: When filtering Conversations by course, when a student and instructor had more shared more than one course, the messages were all filtered into the course with the lower ID number and were not visible as part of the other course. This behavior occurred because the updated time was not preloaded as part of the filter context, pulling older conversations that were no longer relevant. Canvas code has been updated to include updated tags as part of conversations context.
Group Conversations
Group lists load quickly in the Conversation drop-down menu.
Explanation: When a user tried to view a group list in Conversations, the list of users was delayed in loading. This behavior occurred because all contexts were being loaded for the group recipients. Canvas code has been updated to refactor group user lists and load only relevant context.
Course Imports
Essay and File Upload Duplication
Essay questions and File Upload questions are not duplicated as part of a course copy.
Explanation: When a quiz is copied into a course twice, and select content is selected in one of the copy types, Essay and File Upload questions were duplicating in the course. This behavior occurred because of an error with quiz question migration IDs. Canvas code has been updated to retain and verify quiz question IDs for course imports.
Syllabus Public Setting
Syllabi that are public on course copy are retained as public.
Explanation: When an instructor enabled the Make the syllabus for this course publicly visible option and copied the course, the syllabus option was not applied as part of the import. This behavior occurred because the public syllabus was not defined as a clonable attribute for course copies. Canvas code has been updated to preserve the public syllabus attribute and compare the settings when copying a course.
Moodle and Graded Discussions
Point values and graded options in Moodle advanced forums are imported to Graded Discussions.
Explanation: When a Moodle file was imported that contained advanced forums (graded discussions), the point value and graded options were not retained. This behavior occurred because Canvas required a more current code element to support Moodle files. Canvas code has been updated to include a more recent Moodle dependency.
Ungraded Discussions and Until Date
Ungraded Discussions retain the Until Date as part of course copies.
Explanation: Course copies were not retaining Until Dates in ungraded discussions, and users were required to adjust the dates manually when the copy had concluded. This behavior occurred because the Until (lock) date was not included as a migration element. Canvas code has been updated to add the lock date as part of course copies.
Blackboard Matching Questions
Matching questions in Blackboard are imported into Canvas quizzes.
Explanation: When a Blackboard file was imported that contained matching questions in a quiz, the quiz displayed an error for the quiz. This behavior occurred because of an error when referencing quiz answer IDs. Canvas code has been updated to ensure the question IDs reference the correct quiz response.
Assignment Group Settings
When copying individual assignments, course copies do not associate updated information from the source course’s assignment group.
Explanation: When copying an individual assignment from a course that is part of an assignment group, instructors encountered a variety of error types. The new course applied rules to drop the lowest grade, even when no rule was set previously, and if the course copy included an assignment group with a changed name, the name would also update in the former course. This behavior occurred because of a change in course copy procedure in a previous release. Canvas code has been updated to copy individual assignments if the group where they were originally copied does not already exist in the destination course.
Course Settings
Instructors and Concluded Enrollments
When a course is concluded, instructors can still view all Course Navigation links.
Explanation: When a course was concluded by Term Dates, instructors could only view navigation items and files/folders available to students. If the instructor hid any Course Navigation links from students, those links were also not able to be viewed after their Term access ended unless the dates were overridden by course dates. This behavior occurred because the course was not verifying enrollment types for instructors. Canvas code has been updated to confirm enrollments within the course and not hide Course Navigation tabs for instructors.
External Apps
Users can view the External Apps tab and add new apps in Course Settings.
Explanation: The External Apps tab generated multiple behaviors within Course Settings. If a user opened Course Settings and the last open tab was External Apps, the apps tab would not load. When viewing an app, if a user repeatedly clicked the Save button when adding an app, multiple app entries were created. Leaving a secret field blank overwrote the external tool with a blank secret. And the external tool configuration screen domain would not display in the Canvas interface. These behaviors occurred because of recent changes made to the External Tools App. Canvas code has been updated to correct necessary configurations and app values
Dashboard
Coming Up Section
The Coming Up section of the Course or User Dashboard indicates the correct time.
Explanation: When they are more available items in the Coming Up section of the Course or User Dashboard sidebar, the link to display more items showed as more in the past week instead of more in the next week. This behavior occurred because the logic was being copied from the Recent Feedback section, which showed the past 2 weeks. Canvas code has been updated to display the correct time adjective.
Discussions
No Title Discussions and TurnitIn IDs
Discussions are not created for a course except through direct activity from a user.
Explanation: Some courses were generating discussions with no titles and no attached users. This behavior occurred in courses with enabled TurnitIn accounts, whose IDs were generating discussions for the course. Canvas code has been updated to only generate assignments via TurnItIn when applicable to the course.
Disappearing Discussion Comments
Editing a discussion reply retains all associated discussion comments.
Explanation: When a discussion reply was edited, all associated comments as part of the thread would disappear in the discussion topic. This behavior affected both threaded and unthreaded discussions and occurred because of a reply capture error. The reply held an instance of the parent attribute, as opposed to just referencing the parent, so the replies were removed when the associated reply was edited. Canvas code has been updated to track and retain replies after the API edit request is complete.
Group Discussion Attachments
Attachments in group discussions are viewable to all group members.
Explanation: When a user attached a file to a discussion topic as part of a group discussion, the attachment was not viewable to the rest of the group. This behavior occurred because the group attachment ID was not a proper group attribute. Canvas code has been updated to mirror behavior in course groups by defining the group attachment ID and copying all appropriate attributes from the parent discussion.
Podcast Link
Users can access discussion podcasts if a discussion includes a video file.
Explanation: The Discussions podcast link broke when instructors added a video file to a discussion from the content selector. This behavior occurred because of a conflict in media definitions for each media type. Canvas code has been updated to leave out media objects if a media attachment is included as a reply.
ePortfolios
Last Updated Timestamp
ePortfolios display the time of the last update.
Explanation: When a user updates an ePortfolio, the last updated field (as seen on the ePortfolios dashboard) was not being updated to reflect the most recent time. This behavior occurred because changes were not set to trigger an update. Canvas code has been updated to touch the last updated field when a change is made to an ePortfolio.
Files
Drag and Drop Files List
When Better File Browsing is enabled, drag-and-drop functionality is enabled for the entire folder window.
Explanation: When an instructor uses drag and drop to add a file to a course with Better File Browsing enabled, the droppable area was sized only as large as the list of files; empty areas were inactive. This behavior was especially noticeable for mostly empty folders and occurred because the drop space wasn’t expanding to the entire area. Canvas code has been updated with CSS to expand the files upload area.
Fullscreen Video Previews
When Better File Browsing is enabled, videos can be previewed in full screen.
Explanation: When a user attempted to preview a video file in full screen, the file disappeared completely but continued playing. This behavior occurred because of a height calculation error in the preview window. Canvas code has been updated to correct the container elements for the preview display.
File Upload Previews
When Better File Browsing is enabled, users can preview a file upload directly after uploading the file.
Explanation: When a user uploaded a file, relevant previews (such as images) did not appear until the page was refreshed. This behavior occurred because of an outdated file in React, a the JavaScript library for building user interfaces in Canvas. Canvas code has been updated with a newer version of React.
Slash in Files URLs
When Better File Browsing is enabled, users can load files with a slash in the URL.
Explanation: When a files URL included a slash, such as canvas.com/files/, the file would not load. This behavior occurred because of an outdated file in React, a the JavaScript library for building user interfaces in Canvas. Canvas code has been updated with a newer version of React.
Moving Files and Duplicate Names
When Better File Browsing is enabled, users are prompted to replace/change the name of a file if it is moved to a location with the same file name.
Explanation: When a user moved a file to a folder that had a file with the same name, Files did not create a prompt to change the name or replace the current file. This behavior occurred because prompts were only coded as part of uploading files. Canvas code has been updated to view duplicate file names for moving files.
Gradebook
Grading Schemes
New grading schemes save with the included data.
Explanation: When a user created a grading scheme and saved the data, the grading scheme was being overwritten with the default scheme data but only affect the first save of the grading scheme; editing and re-saving the scheme retained all data changes. This behavior occurred because of a misalignment with grading standard IDs. Canvas code has been updated to clarify default data and grading standard IDs. Additionally, users cannot delete a grading scheme row if it is the last remaining row in the grading scheme, and when users save or delete a grading scheme, a confirmation message appears at the top of the window.
Modules
Module Menu Files Limit
When adding a file to a Module, users can choose from all files in the Files list.
Explanation: When a user added a file to a Module, some files in root folders were not appearing in the Files list. This behavior occurred because of an inconsistency in the API. Canvas code has been updated to support files as a React component, which is a JavaScript library for building user interfaces in Canvas. This change creates a folder and file store for interacting with the API and ensures that folders that do not contain any files are not shown in the Modules file list.
Group Discussions and Page Completion Requirement
Group discussion module items with the users must contribute to the page requirement show the module progression checkmark when the requirement is complete.
Explanation: When a Group Discussion assignment type was included in a module, and users were required to contribute to the group discussion before the assignment could be completed, the module item was not displaying the completed check mark and did not allow the student to progress to the next module item. Users were required to change the assignment type to submit the assignment in order for the permission to apply correctly. This behavior occurred because Modules were not coded to accept completions for course assessments in a group context. Canvas code has been updated to forward group actions to the main course discussion.
Manual Quiz Grades
When an instructor manually grades a quiz that is part of a module progress, students can advance to the next module requirement.
Explanation: When an instructor manually awarded points to a student for a quiz in the Gradebook, and the quiz was part of a module requirement, the Module did not allow the student to progress to the next module. This behavior occurred from an inconsistency in manual grading; in assignments, students could be rewarded a grade for a non-submitted assignment and accept the grade as a submission. Canvas code has been updated to evaluate quiz module tags and allow for manual grading to unlock quiz module requirements.
Module Pages and State Changes
Modifying the name of a page as well as the state of a page in Modules does not create duplicate pages.
Explanation: When an instructor added a new page to a module, published the page, changed the name of the page, and unpublished the page, the page was created as a duplicate in the Pages Index page. This behavior occurred because of a misalignment in page IDs. Canvas code has been updated to confirm all page IDs when modifying a page.
Notifications
Designer Role and Grading Assignments
Designers do not receive notifications to grade assignments unless they have permission to edit or view grades.
Explanation: In the To Do sidebar of the Course Dashboard, Course Designers were viewing notifications to grade assignments. This behavior occurred because enrollments were only coded as admin and student enrollment types, where Designer was grouped in the admin type. Canvas code has been updated to refactor grading notifications; grading is also specified by instructor and student course IDs to show graded assignments only to instructors.
Groups and Unpublished Courses
Students do not receive notifications for group membership unless the course is published.
Explanation: If a student was enrolled in an unpublished course and the instructor assigned the user to a group, the student was receiving a notification about the group membership, allowing the student to access the group before the course was published. This behavior occurred because Canvas was not confirming if the course was available (active) before sending notifications. Canvas code has been updated to not send group membership notifications for unpublished courses.
Outcomes
Prior Outcome Creation Warning
Users cannot edit outcomes that have been used to assess a student.
Explanation: When users tried to edit an outcome that had already been used to assess a student, such as modifying the title, description, or point scale, Canvas generated an error message. This behavior occurred because of a change made to the Outcomes API on January 31, 2015, which set the assessment type default value as highest score, and some users wanted to adjust existing outcomes. Canvas does not allow outcomes to be modified if they have already been used to assess a student. Canvas code has been updated to disable the edit button for outcomes that cannot be modified within a course or account.
Account-level Outcomes
Users can view account-level outcomes if they have permission to view the page.
Explanation: When a user with permission to view account-level outcomes tried to view an outcome, Canvas generated a page error. This behavior occurred because the outcome was not properly aligning with the account. Canvas code has been updated to update the outcome alignment URL to allow context showing it is an account outcome. This fix was deployed to production on March 26.
Pages
Content Selector and Student Pages
Students can edit course pages if they are given permission in the course.
Explanation: When a course allowed students to create pages, students were able to insert a new page from the content selector, but the page could not be saved. This behavior occurred because of an inconsistency with the permission to edit course pages and the account-level permission to manage pages. Canvas code has been updated to confirm permissions to manage pages as part of course page edits.
Pages and Periods in Titles
Pages supports pages with periods in the title.
Explanation: When an instructor used the content selector to create a new link to a new page, putting a period in the page title caused a page error. This behavior occurred because periods were not a supported symbol in page titles. Canvas code has been updated to support periods in page titles.
Profiles
Report Inappropriate Picture Link in Profiles
The Report Inappropriate Picture link always appears next to a profile picture.
Explanation: When profiles were enabled at the account level, the Report Inappropriate Picture link did not appear. However, when Profiles were disabled, the link returned by the listing. This behavior occurred because of an error in the reporting links. Canvas code has been updated to include the Report Inappropriate Picture link for all profile picture listings, no matter if Profiles is enabled for the account.
Report Inappropriate Picture Link
Then Report Inappropriate Picture button reports a profile image as reported.
Explanation: When a user clicked the Report Inappropriate Pictures button on a user’s profile, the button displayed an error message stating the image was not reported. This behavior occurred because of an error in the action response for the button. Canvas code has been updated to correct the click action and add a confirmation message that the reporting was successful.
Rich Content Editor
Whitelist Language Tag
The language tag is retained as a whitelist element in the Rich Content Editor.
Explanation: When a user attempted to add an HTML comment, the language tag was being filtered about by the HTML editor. This behavior occurred because of an error in the Canvas whitelist sanitization dependency. Canvas code has been updated to support the language tag in the Canvas whitelist and all HTML elements.
Next release schedule:
-
Beta release and notes: 04/13/15
-
Production release notes: 04/20/15
-
Production release and documentation: 04/25/15
Note: You can follow the release schedule on the Canvas Updates calendar