Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conflict with Olark due to language attribute #36

Closed
andrewboni opened this issue Jan 8, 2015 · 8 comments · Fixed by #52
Closed

Conflict with Olark due to language attribute #36

andrewboni opened this issue Jan 8, 2015 · 8 comments · Fixed by #52

Comments

@andrewboni
Copy link

Hi, we use Olark on our site in order to chat with users. Seems that Olark injects the following code:

<script language="javascript" id="...

Angular highlightjs is also looking for this language= directive, which causes a conflict:

 Exception  Error: [$compile:ctreq] http://errors.angularjs.org/1.2.27/$compile/ctreq?p0=hljs&p1=language
Controller 'hljs', required by directive 'language', can't be found!

Any thoughts on how to properly resolve this? Thanks!

@pc035860
Copy link
Owner

Hi @stormbytes

The issue can be easily resolved through setting the hljs controller requirement to be optional in those directives. But I'm also considering prefixing directive names with hljs-.

Do you think I should rename all related directive/attribute names or just directive names?

directive names

  • language
  • source
  • include

attribute names

  • compile
  • escape
  • no-escape
  • onhighlight

pc035860 added a commit that referenced this issue Jan 11, 2015
@pc035860
Copy link
Owner

Hey @andrewboni , v0.3.3 should work without errors now.

@andrewboni
Copy link
Author

Great- taking a look now.

@andrewboni
Copy link
Author

@pc035860 seems to be working- thanks for the fast resolution! Will let you know if I encounter anything else.

@andrewboni
Copy link
Author

+1 agreed

On Mon, Jan 12, 2015 at 4:16 PM, Daniel Balfour [email protected]
wrote:

Def a better idea to prefix attr-names


Reply to this email directly or view it on GitHub
#36 (comment)
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants
@andrewboni @pc035860 and others