- Makes the action buttons underneath problems into link buttons
instead of push buttons. Per UI team
- Updates some colors of status pills like "Past due" or "Completed"
This will fix a bug about if assignment type is None, we will only
show the due date.
This will also fix a bug where we would show the assignment type and
due date on non-scored units within a subsection. Now it will only
show on scored units.
This also fixes the pill that displays from stretching out if the due
date text is multi-lined.
updated css
temp fixex
Updated js code for data download
updated js hooks for new UI
fixed ui and navigation
reset paver file
Removed unused changes
Initial tests added
Initial tests added
fixed style issues
Created new tests for data download
Fixed A11y and quality issues
Updated test file and removed new
fixed Accesibility issues
fixed code style in spec
removed old data download file
Moved problem grade report
Updated html to fix accessiblity issue
Fixed accessiblity issues
Created waffle flag for data download
added doc strign in doc
renamed waffles file
Break down Html and fixed tests
Removed extra js and updated comments
Removed extra js and updated comments
renamed var fixed styling
fixed js test fail
Fixed styling issues
updated description texts
Updated problem selector UI
Fixed Jest test for react component
removed depricated default param
added class instead of style
updated snapshot
Co-authored-by: Awais Jibran <awaisdar001@gmail.com>
This also has an initial use case for Personalized Learner Schedules
to add CTAs to capa and vertical blocks to allow users to shift their
course deadlines.
ORA2 (openassessment) problems have multiple dates associated with are
not bound to the `due` date that is modified by Personalized Learner
Schedules. We expose the ORA2 dates separately in the dates page
so that learners aren't surprised by the differing deadlines.
[AA-223]
Due dates will only display for graded subsections.
If the assignment has already been completed, there will be a pill
to indicate that. If the assignment is past due, there will be a
pill. If it is upcoming, there are no pills
- use new dates banner template on course outline page
- remove old banner from main.html
- let dates tab use new dates banner template
- remove dates banner completely from the courseware problem view
on the web app
- use new banner on the courseware problem view on the mobile app
- update banner util to use get_course_blocks
Added a banner to introduce learners to the Dates Tab.
The banner is hidden when the learner has missed deadlines.
Refactored naming conventions in the dates sass file to better
reflect the function of our banners.
AA-156
* Fix all stylelint errors
For any errors that fixing would require changing the output of the css disable stylelint for that line instead of modifying.
* Update quality.py
Make stylelint quality check pass when there are no errors
* Delete empty selectors
The dates tab has a lot of redundant calls to action around
upgrading to verified track. This replaces them with a single
banner at the top of the page.
AA-102
- remove code for displaying banner in mobile dates fragment
- replace button with link to web app in reset dates banner on
the mobile problem template
- adjust spacing of reset dates button in banner when button wraps
on smaller screen
- for self paced courses, if a sequential's due date has passed
and it is incomplete, allow the user to reset the start_date
for the related schedule to now, thus shifting all due dates
for all sequentials within the course by the pre determined
due date offset.
- add historical table to the Schedule model.
Recent google chrome updates showing awkard alignments on table.To
avoid them modifications in word-break css property are carried out
so that usability of content remains coherent on all browsers.
PROD-185
The banner took up too much room with the browser
zoomed in. This adds a button to hide/show much of the copy, reducing the
portion of the page on zoomed-in desktop browsers stickily obscuring
courseware. The toggle's initial state is set according to browser
width.
update semantic structure of some proctoring banner elements
JIRA:EDUCATOR-3899
JIRA:EDUCATOR-3900
The course_visiblity field can have one of three values:
1. private (default): This keeps the standard access rules.
2. public_outline: Allows unenrolled and anonymous users access to the outline.
3. public: Allows unenrolled and anonymous users access to both outline and
course content.
When an unenrolled user accesses course content, instead of student_view(),
public_view() is used. A default implementation is provided for XBlocks
which do not implement this view. The public_view() must not have any
functionality which assumes the presence of a valid User and should show
a readonly only interface for the XBlock content.
