marcelodolza/iziModal

console errors when working with angularjs

Open

#104 opened on Jul 12, 2017

View on GitHub
 (0 comments) (0 reactions) (0 assignees)CSS (2,146 stars) (291 forks)batch import
help wanted

Description

I've tried just to add the iziModal library to my code, and it throws errors to the console when toggling between routes

  • without the plugin inside the bundle, the console is clean and works cleanly.

Error: Syntax error, unrecognized expression: #/users/ at Function.fa.error (vendor-scripts.min.js:2) at fa.tokenize (vendor-scripts.min.js:2) at fa.select (vendor-scripts.min.js:2) at Function.fa [as find] (vendor-scripts.min.js:2) at n.fn.init.find (vendor-scripts.min.js:2) at n.fn.init (vendor-scripts.min.js:2) at n (vendor-scripts.min.js:2) at vendor-scripts.min.js:3040 at dispatch (vendor-scripts.min.js:3) at r.handle (vendor-scripts.min.js:3)

Contributor guide

Tech stack
javascriptcss
Domain
frontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
JavaScriptjQuery
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80
Research direction
The error 'Syntax error, unrecognized expression: #/users/' indicates that jQuery's selector parser is interpreting the hash character as a CSS selector when the modal tries to find elements. This typically occurs when a selector like '#/users/' is passed to jQuery. Investigate the iziModal source code (likely in the main JavaScript file) where selectors are used. Look for any place where a hash symbol appears in a selector string, possibly from URL routes in AngularJS. The fix may involve escaping the hash or using a different method to locate elements.