Open gioman opened 7 years ago
@volaya this looks like yours
The app in that zip file works perfectly with no error in the js console, both if i open it directly or if i serve ir (using python SimpleHTTPServer)
How do you get that error, @bartvde
Line 410 is correct, but apparently missing a semicolon at the end. I I fixed that. Maybe your browser (I am using Chrome) is less tolerant to that?
@volaya possibly, this report is specific for IE11, on other browsers (FF, Chrome) is ok.
right this was IE, and IE is sensitive to that
so probably needs to be retested on WAB master right?
@bartvde @volaya even with changes that fixed https://github.com/boundlessgeo/qgis-webappbuilder-plugin/issues/409 this is a no go
ok checking your zips
yeah I get the same in IE11
can we pinpoint this somehow to some of the functionality @gioman I wonder if it's caused by the rendering extensions or something else
the webapp has no widgets, overlays or basemaps active.
can we check a project without the rendering extensions in it?
@volaya this is only added in the basic theme right?
can we check a project without the rendering extensions in it?
I have checked several simple projects and beside a few glitches/problems (see layer list) they worked on IE11.
@gioman can you check this exact same project with the tabbed theme?
it's caused by the pattern fills based on svg
@bartvde so no need to test the tabbed version?
@bartvde @volaya trying to compile this project in tabbed mode fails:
2017-05-31T08:04:44 2 WebAppBuilder: Cannot build webapp: Network error #400: Error downloading https://api.boundlessgeo.io/v1/websdk/package - server replied: SyntaxError: /tmp/websdk/f3064414-eaa9-46b6-bffc-61d24b906ba8/webapp/app.jsx: Unexpected token (2017:109)
ref:"table", pointZoom:16, map: map,
sortable:true, pageSize:20})
)], open: this.state.leftNavOpen, onRequestClose: this.leftNavClose.bind(this}),
React.createElement("div", undefined,
React.createElement(Header, toolbarOptions ),
React.createElement("div", {className: 'map', style: {left: this.state.leftNavOpen ? leftNavWidth : 0, width: this.state.leftNavOpen ? 'calc(100% - ' + leftNavWidth + 'px)' : '100%'}},
at Parser.pp.raise (/tmp/websdk/f3064414-eaa9-46b6-bffc-61d24b906ba8/webapp/node_modules/babylon/lib/parser/location.js:24:13)
at Parser.pp.unexpected (/tmp/websdk/f3064414-eaa9-46b6-bffc-61d24b906ba8/webapp/node_modules/babylon/lib/parser/util.js:82:8)
at Parser.pp.expect (/tmp/websdk/f3064414-eaa9-46b6-bffc-61d24b906ba8/webapp/node_modules/babylon/lib/parser/util.js:76:33)
at Parser.pp.parseExprList (/tmp/websdk/f3064414-eaa9-46b6-bffc-61d24b906ba8/webapp/node_modules/babylon/lib/parser/expression.js:785:12)
at Parser.pp.parseSubscripts (/tmp/websdk/f3064414-eaa9-46b6-bffc-61d24b906ba8/webapp/node_modules/babylon/lib/parser/expression.js:270:29)
at Parser.pp.parseExprSubscripts (/tmp/websdk/f3064414-eaa9-46b6-bffc-61d24b906ba8/webapp/node_modules/babylon/lib/parser/expression.js:240:17)
at Parser.pp.parseMaybeUnary (/tmp/websdk/f3064414-eaa9-46b6-bffc-61d24b906ba8/webapp/node_modules/babylon/lib/parser/expression.js:217:19)
at Parser.pp.parseExprOps (/tmp/websdk/f3064414-eaa9-46b6-bffc-61d24b906ba8/webapp/node_modules/babylon/lib/parser/expression.js:163:19)
at Parser.pp.parseMaybeConditional (/tmp/websdk/f3064414-eaa9-46b6-bffc-61d24b906ba8/webapp/node_modules/babylon/lib/parser/expression.js:145:19)
at Parser.pp.parseMaybeAssign (/tmp/websdk/f3064414-eaa9-46b6-bffc-61d24b906ba8/webapp/node_modules/babylon/lib/parser/expression.js:112:19)
can you attach the app.jsx file?
can you attach the app.jsx file?
This can be fixed by exporting svgs to pngs like we do for markers. However, this might not be ready for release, so I suggest leaving it like that and documenting this limitation (svg pattern fills + IE).
I have opened a JIRA ticket to address this later and not forget about it
@SrNetoChan what o you think?
@volaya I have documented in here:
Is it ok?
ah looks to be the trailing frontal comma on the tablist:
tabList: [,
React.createElement```
no sorry it's this line:
this.leftNavClose.bind(this})
will fix in WAB
Seen trough a web server (apache). This is the webapp as generated by the new manual test (tester plugin) "osm".
cb8876bcc68d4ea4b4a878b87f078c26.zip