Hello,

The sfdc.css file is associated in the DITA Map framework, right? If you put it last in the list of associated CSSs then it should override the content property just as expected. Please check if that's indeed true.

Anyway, it might also help to add an !important flag (although using the right order is more desirable):

*[class~='topic/data'][name]:before {
    content : " " !important;
}

Best regards,
Alex
-- 
Alex Jitianu
<oXygen/>  XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com 

Thanks for the tips.  I did find one problem that I'm trying to figure out a low impact solution for.  In the CSS Inspector I see:

-topic-specialization.css:40

*[class~='topic/data'][name]:before {

-oxy-append-content : oxy_textfield(edit , "@name" , columns , 10) ;

}

sfdc.css:11

*[class~='topic/data'][name]:before {

content : " " ;

}

I'm setting the content to a zero length string, but the oxy-append adds to that zero space string. How do I force the author to ignore the append-content instruction?  I'd like to avoid having to modify topic-specializaton.css.

     - Steve

On Fri, Sep 7, 2018 at 6:45 AM, Alex Jitianu <alex_jitianu@sync.ro> wrote:

Hello,

Same issue for the value field; if I want to hide it, how can I hide it?

I almost missed this part. In the same way, by using the CSS Inspector, you can identify the offending rules and write your own rules to override them. For your needs, it might be easier to keep your rule on the :after (like you did) and just reset everything the other rules are contributing on the :before :

map > topicmeta > data-about > data[name="icon_url"]:after {
     content: "Pick a local icon or a remote URL for the icon:"
        oxy_urlChooser(       
        edit, "@href",
        columns 50);
}      


 map > topicmeta > data-about > *[class~='topic/data']:before {
 content : " "  ;
}

Best regards,
Alex
-- 
Alex Jitianu
<oXygen/>  XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com 

On 9/7/2018 4:26 PM, Alex Jitianu wrote:

Hello,

You are still seeing the other form control because that one is added on a :before pseudo element while yours is added on an :after .

You should change the rule to override the :before element like this:

map > topicmeta > data-about > data[name="icon_url"]:before {
     content: "Pick a local icon or a remote URL for the icon:"
        oxy_urlChooser(       
        edit, "@href",
        columns 50);
}

The CSS Inspector view [1] is quite useful to debug such situations.

[1] https://www.oxygenxml.com/doc/versions/20.1/ug-editor/topics/author-css-inspector-view.html

Best regards,
Alex
-- 
Alex Jitianu
<oXygen/>  XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com 

On 9/7/2018 12:57 AM, Steven Anderson wrote:

In my DITA topic I have the following:

<map xml:lang="en-us" linking="none">

 <title>Title</title>

 <topicmeta>

  <shortdesc>shortdesc</shortdesc>

  <data-about>

   <data name="icon_url" href="http://<some_path>"/>

In author view, by default, I see a form field for the name.  I'd like to override that using CSS.

I figured out how to do 

map > topicmeta > data-about > data[name="icon_url"]:after {

     content: "Pick a local icon or a remote URL for the icon:"

        oxy_urlChooser(        

        edit, "@href",

        columns 50);

}       

which allows me to show a picker for an attribute I do want to display, but, I still see the form field for the name attribute.  

Same issue for the value field; if I want to hide it, how can I hide it?

--

     Steve

_______________________________________________
oXygen-user mailing list
oXygen-user@oxygenxml.com
https://www.oxygenxml.com/mailman/listinfo/oxygen-user

_______________________________________________
oXygen-user mailing list
oXygen-user@oxygenxml.com
https://www.oxygenxml.com/mailman/listinfo/oxygen-user

_______________________________________________
oXygen-user mailing list
oXygen-user@oxygenxml.com
https://www.oxygenxml.com/mailman/listinfo/oxygen-user

--

     Steve