Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exam mode: Fix an issue where the end page of exam does not scroll when the page is too small #8916

Merged
merged 2 commits into from
Jun 30, 2024

Conversation

edkaya
Copy link
Contributor

@edkaya edkaya commented Jun 28, 2024

Checklist

General

Client

  • I strictly followed the client coding and design guidelines.
  • Following the theming guidelines, I specified colors only in the theming variable files and checked that the changes look consistent in both the light and the dark theme.
  • I added multiple screenshots/screencasts of my UI changes.

Motivation and Context

In the end page of student view of exam mode, users can not scroll down if the page gets too small.

Description

I added a scrollbar if the user is currently in the end page of an exam.

Steps for Testing

Prerequisites:

  • 1 Student
  • 1 Exam
  1. Log in to Artemis
  2. Participate the exam
  3. Click on Hand in Early
  4. Verify that you can scroll down if the page gets too small in height

Exam Mode Testing

Prerequisites:

  • 1 Student
  • 1 Exam
  1. Log in to Artemis
  2. Participate in the exam as a student
  3. Make sure that the UI of other components in the exam mode stays unchanged. You can use the exam mode documentation as reference.

Testserver States

Note

These badges show the state of the test servers.
Green = Currently available, Red = Currently locked
Click on the badges to get to the test servers.







Review Progress

Code Review

  • Code Review 1
  • Code Review 2

Manual Tests

  • Test 1
  • Test 2

Exam Mode Test

  • Test 1
  • Test 2

Screenshots

Screenshot 2024-06-28 at 19 33 23

Summary by CodeRabbit

  • New Features

    • Introduced end view tracking for exams, enhancing the monitoring and display of exam completion status.
  • Style

    • Added new styles for exam end view and adjusted hover behavior for specific anchor tags, improving UI consistency.
  • Bug Fixes

    • Ensured proper display of text content in exam cover component based on exam view status.
  • Tests

    • Updated test mocks to support new end view tracking functionality.

@edkaya edkaya requested a review from a team as a code owner June 28, 2024 17:34
@edkaya edkaya linked an issue Jun 28, 2024 that may be closed by this pull request
@github-actions github-actions bot added the client Pull requests that update TypeScript code. (Added Automatically!) label Jun 28, 2024
Copy link

coderabbitai bot commented Jun 28, 2024

Walkthrough

The changes implement functionality to manage the display state of an exam's end view in the application. Key updates involve introducing a boolean flag in the ExamParticipationCoverComponent to control view states, subscribing and tracking the end view state within components, and adding corresponding styles. Additionally, mock services were updated to accommodate these changes for testing purposes.

Changes

File(s) Change Summary
.../exam/participate/exam-cover/... Introduced boolean flag handling end view state in ExamParticipationCoverComponent.
.../exam/participate/exam-participation.service.ts Added examEndViewSubject BehaviorSubject, endViewDisplayed$ observable, and setEndView method to manage end view state.
.../overview/course-overview.component.html Added conditional class for styling based on isExamEndView variable.
.../overview/course-overview.component.scss Introduced .exam-end-view styling and modified link styling for specific classes on hover.
.../overview/course-overview.component.ts Implemented isExamEndView tracking, including subscription and unsubscription in component lifecycle methods.
.../mocks/service/mock-exam-participation.service.ts Added examEndViewSubject BehaviorSubject and setEndView method to mock service for testing purposes.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant CourseOverviewComponent
    participant ExamParticipationService
    participant ExamParticipationCoverComponent

    User ->> CourseOverviewComponent: Load Course Overview
    CourseOverviewComponent ->> ExamParticipationService: Subscribe to endViewDisplayed$
    ExamParticipationService -->> ExamParticipationCoverComponent: Notify end view state
    ExamParticipationCoverComponent ->> ExamParticipationCoverComponent: Set boolean flag based on end view state
    ExamParticipationCoverComponent -->> CourseOverviewComponent: Apply end view class if true
Loading
sequenceDiagram
    participant User
    participant ExamParticipationService
    participant MockExamParticipationService

    User ->> ExamParticipationService: setEndView(true/false)
    ExamParticipationService ->> ExamParticipationService: Update examEndViewSubject
    MockExamParticipationService ->> MockExamParticipationService: Simulate end view state change with examEndViewSubject
Loading

Recent review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE

Commits

Files that changed from the base of the PR and between 4168203 and b4e0a3f.

Files selected for processing (6)
  • src/main/webapp/app/exam/participate/exam-cover/exam-participation-cover.component.ts (1 hunks)
  • src/main/webapp/app/exam/participate/exam-participation.service.ts (2 hunks)
  • src/main/webapp/app/overview/course-overview.component.html (1 hunks)
  • src/main/webapp/app/overview/course-overview.component.scss (1 hunks)
  • src/main/webapp/app/overview/course-overview.component.ts (3 hunks)
  • src/test/javascript/spec/helpers/mocks/service/mock-exam-participation.service.ts (2 hunks)
Additional context used
Path-based instructions (5)
src/test/javascript/spec/helpers/mocks/service/mock-exam-participation.service.ts (1)

Pattern src/test/javascript/spec/**/*.ts: jest: true; mock: NgMocks; bad_practices: avoid_full_module_import; perf_improvements: mock_irrelevant_deps; service_testing: mock_http_for_logic; no_schema: avoid_NO_ERRORS_SCHEMA; expectation_specificity: true; solutions: {boolean: toBeTrue/False, reference: toBe, existence: toBeNull/NotNull, undefined: toBeUndefined, class_obj: toContainEntries/toEqual, spy_calls: {not_called: not.toHaveBeenCalled, once: toHaveBeenCalledOnce, with_value: toHaveBeenCalledWith|toHaveBeenCalledExactlyOnceWith}}

src/main/webapp/app/exam/participate/exam-cover/exam-participation-cover.component.ts (1)

Pattern src/main/webapp/**/*.ts: angular_style:https://angular.io/guide/styleguide;methods_in_html:false;lazy_loading:true;code_reuse:true;tests:meaningful;types:PascalCase;enums:PascalCase;funcs:camelCase;props:camelCase;no_priv_prefix:true;strings:single_quotes;localize:true;btns:functionality;links:navigation;icons_text:newline;labels:associate;code_style:arrow_funcs,curly_braces,open_braces_same_line,indent_4;memory_leak_prevention:true;routes:naming_schema;chart_framework:ngx-charts;responsive_layout:true

src/main/webapp/app/overview/course-overview.component.html (1)

Pattern src/main/webapp/**/*.html: @if and @for are new and valid Angular syntax replacing *ngIf and *ngFor. They should always be used over the old style.

src/main/webapp/app/exam/participate/exam-participation.service.ts (1)

Pattern src/main/webapp/**/*.ts: angular_style:https://angular.io/guide/styleguide;methods_in_html:false;lazy_loading:true;code_reuse:true;tests:meaningful;types:PascalCase;enums:PascalCase;funcs:camelCase;props:camelCase;no_priv_prefix:true;strings:single_quotes;localize:true;btns:functionality;links:navigation;icons_text:newline;labels:associate;code_style:arrow_funcs,curly_braces,open_braces_same_line,indent_4;memory_leak_prevention:true;routes:naming_schema;chart_framework:ngx-charts;responsive_layout:true

src/main/webapp/app/overview/course-overview.component.ts (1)

Pattern src/main/webapp/**/*.ts: angular_style:https://angular.io/guide/styleguide;methods_in_html:false;lazy_loading:true;code_reuse:true;tests:meaningful;types:PascalCase;enums:PascalCase;funcs:camelCase;props:camelCase;no_priv_prefix:true;strings:single_quotes;localize:true;btns:functionality;links:navigation;icons_text:newline;labels:associate;code_style:arrow_funcs,curly_braces,open_braces_same_line,indent_4;memory_leak_prevention:true;routes:naming_schema;chart_framework:ngx-charts;responsive_layout:true

Biome
src/main/webapp/app/exam/participate/exam-cover/exam-participation-cover.component.ts

[error] 100-100: Forbidden non-null assertion.

(lint/style/noNonNullAssertion)


[error] 100-100: Forbidden non-null assertion.

(lint/style/noNonNullAssertion)


[error] 100-100: Forbidden non-null assertion.

(lint/style/noNonNullAssertion)


[error] 102-102: Forbidden non-null assertion.

(lint/style/noNonNullAssertion)


[error] 102-102: Forbidden non-null assertion.

(lint/style/noNonNullAssertion)


[error] 102-102: Forbidden non-null assertion.

(lint/style/noNonNullAssertion)


[error] 104-104: Forbidden non-null assertion.

(lint/style/noNonNullAssertion)


[error] 104-104: Forbidden non-null assertion.

(lint/style/noNonNullAssertion)


[error] 109-109: Change to an optional chain.

Unsafe fix: Change to an optional chain.

(lint/complexity/useOptionalChain)


[error] 149-149: Forbidden non-null assertion.

(lint/style/noNonNullAssertion)


[error] 149-149: Forbidden non-null assertion.

Unsafe fix: Replace with optional chain operator ?. This operator includes runtime checks, so it is safer than the compile-only non-null assertion operator

(lint/style/noNonNullAssertion)


[error] 149-149: Forbidden non-null assertion.

(lint/style/noNonNullAssertion)


[error] 153-153: Forbidden non-null assertion.

(lint/style/noNonNullAssertion)


[error] 153-153: Forbidden non-null assertion.

Unsafe fix: Replace with optional chain operator ?. This operator includes runtime checks, so it is safer than the compile-only non-null assertion operator

(lint/style/noNonNullAssertion)


[error] 153-153: Forbidden non-null assertion.

(lint/style/noNonNullAssertion)


[error] 153-153: Forbidden non-null assertion.

(lint/style/noNonNullAssertion)


[error] 156-156: Forbidden non-null assertion.

(lint/style/noNonNullAssertion)


[error] 156-156: Forbidden non-null assertion.

Unsafe fix: Replace with optional chain operator ?. This operator includes runtime checks, so it is safer than the compile-only non-null assertion operator

(lint/style/noNonNullAssertion)


[error] 156-156: Forbidden non-null assertion.

(lint/style/noNonNullAssertion)


[error] 178-178: Change to an optional chain.

Unsafe fix: Change to an optional chain.

(lint/complexity/useOptionalChain)

src/main/webapp/app/exam/participate/exam-participation.service.ts

[error] 61-61: Template literals are preferred over string concatenation.

Unsafe fix: Use a template literal.

(lint/style/useTemplate)


[error] 84-84: Template literals are preferred over string concatenation.

Unsafe fix: Use a template literal.

(lint/style/useTemplate)


[error] 125-125: Template literals are preferred over string concatenation.

Unsafe fix: Use a template literal.

(lint/style/useTemplate)


[error] 135-135: Template literals are preferred over string concatenation.

Unsafe fix: Use a template literal.

(lint/style/useTemplate)


[error] 146-146: Template literals are preferred over string concatenation.

Unsafe fix: Use a template literal.

(lint/style/useTemplate)


[error] 169-169: Forbidden non-null assertion.

Unsafe fix: Replace with optional chain operator ?. This operator includes runtime checks, so it is safer than the compile-only non-null assertion operator

(lint/style/noNonNullAssertion)


[error] 172-172: Forbidden non-null assertion.

(lint/style/noNonNullAssertion)


[error] 182-182: Template literals are preferred over string concatenation.

Unsafe fix: Use a template literal.

(lint/style/useTemplate)


[error] 190-194: This else clause can be omitted because previous branches break early.

Unsafe fix: Omit the else clause.

(lint/style/noUselessElse)


[error] 192-194: This else clause can be omitted because previous branches break early.

(lint/style/noUselessElse)


[error] 200-200: Forbidden non-null assertion.

Unsafe fix: Replace with optional chain operator ?. This operator includes runtime checks, so it is safer than the compile-only non-null assertion operator

(lint/style/noNonNullAssertion)


[error] 205-205: Avoid the delete operator which can impact performance.

Unsafe fix: Use an undefined assignment instead.

(lint/performance/noDelete)


[error] 208-208: Avoid the delete operator which can impact performance.

Unsafe fix: Use an undefined assignment instead.

(lint/performance/noDelete)


[error] 215-215: Avoid the delete operator which can impact performance.

Unsafe fix: Use an undefined assignment instead.

(lint/performance/noDelete)


[error] 218-218: Avoid the delete operator which can impact performance.

Unsafe fix: Use an undefined assignment instead.

(lint/performance/noDelete)


[error] 219-219: Avoid the delete operator which can impact performance.

Unsafe fix: Use an undefined assignment instead.

(lint/performance/noDelete)


[error] 223-223: Avoid the delete operator which can impact performance.

Unsafe fix: Use an undefined assignment instead.

(lint/performance/noDelete)


[error] 200-200: Excessive complexity detected.

Please refactor this function to reduce its complexity score from 42 to the max allowed complexity 25.

(lint/complexity/noExcessiveCognitiveComplexity)


[error] 267-267: Template literals are preferred over string concatenation.

Unsafe fix: Use a template literal.

(lint/style/useTemplate)


[error] 272-272: Template literals are preferred over string concatenation.

Unsafe fix: Use a template literal.

(lint/style/useTemplate)

src/main/webapp/app/overview/course-overview.component.ts

[error] 115-115: This type annotation is trivially inferred from its initialization.

Safe fix: Remove the type annotation.

(lint/style/noInferrableTypes)


[error] 122-122: This type annotation is trivially inferred from its initialization.

Safe fix: Remove the type annotation.

(lint/style/noInferrableTypes)


[error] 130-130: This type annotation is trivially inferred from its initialization.

Safe fix: Remove the type annotation.

(lint/style/noInferrableTypes)


[error] 131-131: This type annotation is trivially inferred from its initialization.

Safe fix: Remove the type annotation.

(lint/style/noInferrableTypes)


[error] 135-135: This type annotation is trivially inferred from its initialization.

Safe fix: Remove the type annotation.

(lint/style/noInferrableTypes)


[error] 145-145: Unexpected any. Specify a different type.

any disables many type checking rules. Its use should be avoided.

(lint/suspicious/noExplicitAny)


[error] 153-153: Unexpected any. Specify a different type.

any disables many type checking rules. Its use should be avoided.

(lint/suspicious/noExplicitAny)


[error] 313-313: Forbidden non-null assertion.

(lint/style/noNonNullAssertion)


[error] 532-532: Forbidden non-null assertion.

(lint/style/noNonNullAssertion)


[error] 542-542: Forbidden non-null assertion.

(lint/style/noNonNullAssertion)


[error] 583-583: Unexpected any. Specify a different type.

any disables many type checking rules. Its use should be avoided.

(lint/suspicious/noExplicitAny)


[error] 599-599: Unexpected any. Specify a different type.

any disables many type checking rules. Its use should be avoided.

(lint/suspicious/noExplicitAny)


[error] 683-685: This else clause can be omitted because previous branches break early.

Unsafe fix: Omit the else clause.

(lint/style/noUselessElse)


[error] 720-720: The assignment should not be in an expression.

The use of assignments in expressions is confusing.
Expressions are often considered as side-effect free.

(lint/suspicious/noAssignInExpressions)


[error] 728-730: This else clause can be omitted because previous branches break early.

Unsafe fix: Omit the else clause.

(lint/style/noUselessElse)


[error] 734-734: Forbidden non-null assertion.

(lint/style/noNonNullAssertion)


[error] 774-774: Template literals are preferred over string concatenation.

Unsafe fix: Use a template literal.

(lint/style/useTemplate)


[error] 781-781: Change to an optional chain.

Unsafe fix: Change to an optional chain.

(lint/complexity/useOptionalChain)


[error] 779-779: Reassigning a function parameter is confusing.

The parameter is declared here:

Use a local variable instead.

(lint/style/noParameterAssign)

Additional comments not posted (10)
src/test/javascript/spec/helpers/mocks/service/mock-exam-participation.service.ts (1)

13-13: Approved addition of BehaviorSubject for managing exam end view state.

src/main/webapp/app/overview/course-overview.component.scss (2)

129-131: Approved addition of .exam-end-view class for scroll functionality.

Ensure that the use of !important is necessary to override specific styles and not a practice used broadly across the stylesheets.


132-132: Approved removal of text decoration on hover for anchor tags.

src/main/webapp/app/exam/participate/exam-cover/exam-participation-cover.component.ts (1)

91-95: Approved use of setEndView to manage exam view state dynamically.

src/main/webapp/app/overview/course-overview.component.html (1)

132-132: Approved conditional application of exam-end-view class.

src/main/webapp/app/exam/participate/exam-participation.service.ts (2)

33-35: Approved addition of BehaviorSubject and Observable for managing exam end view state.


357-359: Approved implementation of setEndView for dynamic state management.

src/main/webapp/app/overview/course-overview.component.ts (3)

124-124: Ensure proper subscription management for examEndViewSubscription.

The subscription to examEndViewSubscription is correctly initialized and unsubscribed. This follows best practices for memory leak prevention in Angular applications by ensuring that all subscriptions are cleaned up in the ngOnDestroy lifecycle hook to prevent memory leaks.

Also applies to: 126-126, 212-214, 765-765


Line range hint 683-685: Consider omitting unnecessary else clauses.

The else clauses following return statements in if blocks are redundant and can be omitted to simplify the flow of the code.

if (condition) {
  return value;
}
- else {
-   // some code
- }

Also applies to: 728-730

Tools
Biome

[error] 122-122: This type annotation is trivially inferred from its initialization.

Safe fix: Remove the type annotation.

(lint/style/noInferrableTypes)


Line range hint 779-779: Avoid reassigning function parameters.

Reassigning function parameters can lead to unexpected behavior and make the code harder to understand. Use a local variable instead.

- function(parameter) {
-   parameter = newValue;
+ function(originalParameter) {
+   const parameter = originalParameter;
Tools
Biome

[error] 122-122: This type annotation is trivially inferred from its initialization.

Safe fix: Remove the type annotation.

(lint/style/noInferrableTypes)


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

⚠️ Unable to deploy to test servers ⚠️

The docker build needs to run through before deploying.

@github-actions github-actions bot added the deployment-error Added by deployment workflows if an error occured label Jun 28, 2024
@github-actions github-actions bot added the tests label Jun 28, 2024
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

Outside diff range comments (5)
src/main/webapp/app/overview/course-overview.component.ts (5)

Line range hint 115-115: Remove redundant type annotations.

TypeScript's type inference means that explicit types for initialized properties are often unnecessary. Consider simplifying the code by removing these redundant type annotations.

- readonly MIN_DISPLAYED_COURSES: number = 6;
+ readonly MIN_DISPLAYED_COURSES = 6;

- readonly WINDOW_OFFSET: number = 300;
+ readonly WINDOW_OFFSET = 300;

- readonly ITEM_HEIGHT: number = 38;
+ readonly ITEM_HEIGHT = 38;

- readonly BREADCRUMB_AND_NAVBAR_HEIGHT: number = 88;
+ readonly BREADCRUMB_AND NAVBAR_HEIGHT = 88;

Also applies to: 122-122, 130-130, 131-131, 135-135

Tools
Biome

[error] 122-122: This type annotation is trivially inferred from its initialization.

Safe fix: Remove the type annotation.

(lint/style/noInferrableTypes)


Line range hint 145-145: Avoid using any type for better type safety.

Using any disables TypeScript's static type checking. Where possible, replace any with more specific types to enhance code robustness and maintainability.

- componentRef: any
+ componentRef: SpecificComponentType // Replace `SpecificComponentType` with the actual expected type.

- activatedComponentReference: any
+ activatedComponentReference: SpecificComponentType // Replace `SpecificComponentType` with the actual expected type.

Also applies to: 153-153, 583-583, 599-599

Tools
Biome

[error] 122-122: This type annotation is trivially inferred from its initialization.

Safe fix: Remove the type annotation.

(lint/style/noInferrableTypes)


Line range hint 313-313: Remove unnecessary non-null assertions.

Non-null assertions override TypeScript's strict null checks and can lead to runtime errors if not used carefully. Ensure that the variables are indeed non-null or handle potential null cases gracefully.

- this.course!.exercises
+ this.course?.exercises

Also applies to: 532-532, 542-542, 734-734

Tools
Biome

[error] 122-122: This type annotation is trivially inferred from its initialization.

Safe fix: Remove the type annotation.

(lint/style/noInferrableTypes)


Line range hint 720-720: Refactor to use template literals and avoid assignments in expressions.

Using template literals enhances readability and maintainability. Additionally, avoid assignments within expressions to reduce potential side-effects and improve clarity.

- '/topic/courses/' + this.courseId + '/quizExercises'
+ `/topic/courses/${this.courseId}/quizExercises`

Also applies to: 774-774

Tools
Biome

[error] 122-122: This type annotation is trivially inferred from its initialization.

Safe fix: Remove the type annotation.

(lint/style/noInferrableTypes)


Line range hint 781-781: Use optional chaining for safer property access.

Optional chaining is a safer way to access nested properties on objects that might be null or undefined. This reduces the risk of runtime errors.

- if (this.route.snapshot.firstChild?.data?.pageTitle)
+ if (this.route.snapshot.firstChild?.data?.pageTitle?)
Tools
Biome

[error] 122-122: This type annotation is trivially inferred from its initialization.

Safe fix: Remove the type annotation.

(lint/style/noInferrableTypes)

@edkaya edkaya removed the deployment-error Added by deployment workflows if an error occured label Jun 28, 2024
Copy link
Contributor

@pzdr7 pzdr7 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested on TS5. The page is scrollable even with a small window 👍

Copy link
Contributor

@SimonEntholzer SimonEntholzer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested on TS1, and works as expected. Code lgtm too

Copy link
Contributor

@egekurt123 egekurt123 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure if that's a scenario we need to address, but if you narrow the page so much that the attached footer disappears, scrolling doesn't work. I assume that no student has such a small screen

Screenshot 2024-06-29 at 10 53 32

@edkaya
Copy link
Contributor Author

edkaya commented Jun 29, 2024

I'm not sure if that's a scenario we need to address, but if you narrow the page so much that the attached footer disappears, scrolling doesn't work. I assume that no student has such a small screen

Screenshot 2024-06-29 at 10 53 32

I don't think it is going to be a problem because I am not sure if such a small screen is a realistic use case, but I can discuss this with @rabeatwork on Monday 👍 Since, this PR only fixing the scroll problem in end page and we don't use this footer in end page, it will not be in the scope of this PR.

@edkaya edkaya requested a review from egekurt123 June 29, 2024 14:35
Copy link
Contributor

@sarpsahinalp sarpsahinalp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code lgtm

Copy link
Contributor

@egekurt123 egekurt123 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code LGTM and works fine on TS3 besides one unrealistic edge case

@edkaya edkaya added this to the 7.3.1 milestone Jun 29, 2024
Copy link
Contributor

@rabeatwork rabeatwork left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maintainer approve

@krusche krusche changed the title Exam Mode: Fix an issue where the end page of exam does not scroll when the page is too small Exam mode: Fix an issue where the end page of exam does not scroll when the page is too small Jun 30, 2024
@krusche krusche merged commit 8e9567a into develop Jun 30, 2024
103 checks passed
@krusche krusche deleted the bugfix/exam-mode/scroll-end-view branch June 30, 2024 08:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bugfix client Pull requests that update TypeScript code. (Added Automatically!) component:Exam Mode ready to merge tests
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

Exam mode: Cannot scroll on Confirm Early Submission page
7 participants