Project

General

Profile

Actions
Copy link

Bug #24919

open

Reporting mode on "Worst report" on block is too eager

Added by Nicolas CHARLES 6 months ago. Updated 15 days ago.

Status:
New
Priority:
N/A
Assignee:
-
Category:
Web - Compliance & node report
Target version:
8.1.9
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No

Description

If a block contains sub blocks; the worst report will take the worst report within each of these block, rather that the worst report of these block

I would have expected that worst report in a case of one sub-block with 25% compliance and one with 100% compliance would be 25% compliance, and not 0
See screenshot

!clipboard-202405252302-reses.png!

Note that I didn't find anything within the documentation to explicit what was the expected result
happens in 8.1, probably before

Files

clipboard-202405252302-reses.png (14.3 KB) clipboard-202405252302-reses.png Nicolas CHARLES, 2024-05-25 23:02
Actions
Copy link
 #1

Updated by Nicolas CHARLES 6 months ago

  • Description updated (diff)
Actions
Copy link
 #2

Updated by Vincent MEMBRÉ 6 months ago

  • Target version changed from 8.1.3 to 8.1.4
Actions
Copy link
 #3

Updated by Vincent MEMBRÉ 5 months ago

  • Target version changed from 8.1.4 to 8.1.5
Actions
Copy link
 #4

Updated by Vincent MEMBRÉ 5 months ago

  • Target version changed from 8.1.5 to 8.1.6
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ 4 months ago

  • Target version changed from 8.1.6 to 8.1.7
Actions
Copy link
 #6

Updated by Vincent MEMBRÉ 2 months ago

  • Target version changed from 8.1.7 to 8.1.8
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ 15 days ago

  • Target version changed from 8.1.8 to 8.1.9
Actions
Copy link

Also available in: Atom PDF