1 |
|
2 | Is your issue related solely to the core library, or is your issue related to an extension? An extension issue must be filed in the extension's repo.
|
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 | A request for help or a requests for a how-to should be directed to Stack Overflow:
|
15 | http://stackoverflow.com/questions/tagged/cytoscape.js
|
16 | -->
|
17 |
|
18 |
|
19 | Bug report
|
20 | Feature request
|
21 |
|
22 |
|
23 |
|
24 |
|
25 |
|
26 |
|
27 | **Environment info**
|
28 |
|
29 | - Cytoscape.js version :
|
30 | - Browser/Node.js & version :
|
31 |
|
32 | **Current (buggy) behaviour**
|
33 |
|
34 |
|
35 |
|
36 |
|
37 | **Desired behaviour**
|
38 |
|
39 |
|
40 |
|
41 |
|
42 | **Minimum steps to reproduce**
|
43 |
|
44 |
|
45 | Write out an overview of what you need to do to reproduce the issue.
|
46 |
|
47 | Fork/clone this JSBin demo and reproduce your issue so that your issue can be addressed quickly:
|
48 | http://jsbin.com/fiqugiq
|
49 |
|
50 | 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:
|
51 |
|
52 | ```js
|
53 | my.code();
|
54 | ```
|
55 | -->
|
56 |
|
57 |
|
58 |
|
59 |
|
60 |
|
61 |
|
62 |
|
63 |
|
64 | **Description of new feature**
|
65 |
|
66 |
|
67 |
|
68 |
|
69 | **Motivation for new feature**
|
70 |
|
71 |
|
72 |
|
73 |
|
74 |
|