-
Notifications
You must be signed in to change notification settings - Fork 23
Expand file tree
/
Copy pathbug_report.yml
More file actions
64 lines (62 loc) · 1.93 KB
/
bug_report.yml
File metadata and controls
64 lines (62 loc) · 1.93 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
name: Bug report
description: File a bug report to help improve Readium CSS
labels: []
type: "Bug"
body:
- type: markdown
attributes:
value: |
Thank you for filing a bug report! Please [search for existing issues](https://github.com/readium/css/issues?q=is:issue) before submitting.
- type: textarea
id: bug-description
attributes:
label: Describe the bug
description: Also, please let us know what your expectations were.
placeholder: A clear and concise description of what the bug is.
validations:
required: true
- type: textarea
id: bug-steps
attributes:
label: How to reproduce?
description: |
Step by step explanation to reproduce the issue in the Test App.
If you can, drag and drop:
- the publication used to reproduce the problem, after zipping it.
- screenshots or a screencast showing the issue
placeholder: |
1. Open book X
2. Go to chapter Y
3. Swipe left twice
4. See error
...
validations:
required: true
- type: input
id: bug-readium-css-version
attributes:
label: Readium CSS version
description: What version of Readium CSS are you running?
validations:
required: true
- type: input
id: bug-platforms
attributes:
label: Platforms
description: On which platform(s) did you reproduce the problem?
validations:
required: true
- type: input
id: bug-browsers
attributes:
label: Browsers
description: On which browser(s) did you reproduce the problem?
validations:
required: true
- type: textarea
id: bug-additional
attributes:
label: Additional context
description: |
Share additional code showing how you use Readium, if relevant. Output logs are useful as well.
If you already went through the codebase to find the bug, you can explain your findings here.