diff options
| author | zsloan | 2023-02-06 15:31:57 -0600 |
|---|---|---|
| committer | GitHub | 2023-02-06 15:31:57 -0600 |
| commit | c7373f8f6f28b0594f9b70853b951dc9a293b24d (patch) | |
| tree | c70de14d21d8ed08573c1b8659b0f802ad1215a4 /issues/trait-page-mapping-bug.gmi | |
| parent | b457c39b20d200529e1b95906ae4e08d347e428f (diff) | |
| download | gn-gemtext-c7373f8f6f28b0594f9b70853b951dc9a293b24d.tar.gz | |
Create trait-page-mapping-bug.gmi
Diffstat (limited to 'issues/trait-page-mapping-bug.gmi')
| -rw-r--r-- | issues/trait-page-mapping-bug.gmi | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/issues/trait-page-mapping-bug.gmi b/issues/trait-page-mapping-bug.gmi new file mode 100644 index 0000000..ba6ea4d --- /dev/null +++ b/issues/trait-page-mapping-bug.gmi @@ -0,0 +1,15 @@ +# Bug when a user quickly clicks "Compute" for mapping on the trait page + +## Tags + +* assigned: zsloan +* type: bug +* priority: high +* status: ongoing +* keywords: mapping, trait-page + +## Description + +The user sometimes gets a 405 error when they click the "Compute" button on the trait page. This is because the page needs to fully load in beforehand, which can take up to a couple seconds. + +I'm not sure how best to address this. The most simple option would be to have the Compute button be greyed out until all the JS is finished loading. I'll probably do this for now, since I'm not sure how else to address the issue of the DataTable needing to load in (since it needs to be in the DOM in order for the sample values to be used in mapping). |