1 |
|
2 | If you do not have a separate GitHub issue for this PR, then fill out the following sections. If you have created a separate issue for this PR, then please link to it instead of filling out the sections.
|
3 | -->
|
4 |
|
5 | **Issue type**
|
6 |
|
7 |
|
8 | Are you submitting a bug report or a feature request?
|
9 |
|
10 | When submitting a bug report, check the following:
|
11 | - The report has a descriptive title.
|
12 | - The bug still exists in most recent version of the library.
|
13 | -->
|
14 |
|
15 |
|
16 | Bug report
|
17 | Feature request
|
18 |
|
19 |
|
20 |
|
21 |
|
22 |
|
23 |
|
24 | **Environment info**
|
25 |
|
26 | - Cytoscape.js version :
|
27 | - Browser/Node.js & version :
|
28 |
|
29 | **Current (buggy) behaviour**
|
30 |
|
31 |
|
32 |
|
33 |
|
34 | **Desired behaviour**
|
35 |
|
36 |
|
37 |
|
38 |
|
39 | **Minimum steps to reproduce**
|
40 |
|
41 |
|
42 | Write out an overview of what you need to do to reproduce the issue.
|
43 |
|
44 | Fork/clone this JSBin demo and reproduce your issue so that your issue can be addressed quickly:
|
45 | http://jsbin.com/fiqugiq
|
46 |
|
47 | If your code to reproduce is only two or three lines, you can write it in the issue instead. Format your code in backtick code blocks like this:
|
48 |
|
49 | ```js
|
50 | my.code();
|
51 | ```
|
52 | -->
|
53 |
|
54 |
|
55 |
|
56 |
|
57 |
|
58 |
|
59 |
|
60 |
|
61 | **Description of new feature**
|
62 |
|
63 |
|
64 |
|
65 |
|
66 | **Motivation for new feature**
|
67 |
|
68 |
|
69 |
|
70 |
|
71 |
|