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

JBIDE-17849 CSS Hyperlinks aren't working on non-WTP projects #343

Closed
wants to merge 1 commit into from

Conversation

vrubezhny
Copy link
Contributor

CSS Files path resolution is fixed, CSS Hyperlink, Create New File Hyperlink are fixed
JUnit test is added in order to test CSS Stylesheets inclusion using absolute and relative URLs

Signed-off-by: vrubezhny vrubezhny@exadel.com

import org.w3c.dom.NodeList;

/**
* Copied from org.eclipse.wst.html.core.internal.htmlcss.URLModelProvider
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If this is a modified(?) copy of some Eclipse/WTP class we should not use the standard JBoss copyright. Please see examples of such modified classes in any xpl packages.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, it's modified a bit, but probably you're right. The most of the class is a copy of URLModelProvider. The only one method (resolveURI()) is modified (it cannot be just overridden because it's static). So, I'll put the comment from the original class here.

CSS Files path resolution is fixed, CSS Hyperlink, Create New File Hyperlink are fixed
JUnit test is added in order to test CSS Stylesheets inclusion using absolute and relative URLs

Signed-off-by: vrubezhny <vrubezhny@exadel.com>
@vrubezhny
Copy link
Contributor Author

I've updated the PR

@alexeykazakov
Copy link
Contributor

Pushed to master.

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 this pull request may close these issues.

None yet

2 participants