[Building Sakai] Web Content Tool Layout Issue

[Neal Caidin]

Release notes will be welcome with open arms. Please send to me and I will give them a good home.

Sounds like an important CSS change between 2.9.1 and 2.9.2 ?

Many thanks,
Neal

On May 20, 2013, at 3:38 PM, Charles Severance <csev at umich.edu> wrote:

> Thanks Gonzalo.   
> 
> The portlet of web content version *is* part of 2.9.2 - so folks will need to tweak their portal.css or we will see the large white space problem.
> 
> Something should be added to the release notes - because folks won't realize that there is a small change to the CSS needed for 2.9.2
> 
> Of course this change does not harm 2.9.1 and earlier.
> 
> /Chuck
> 
> On May 20, 2013, at 2:42 PM, Gonzalo Silverio wrote:
> 
>> Hi!
>> 
>> This is a simple enough thing, but has some complexities.
>> 
>> I will refer to the screenshot.
>> 
>> Notice that there is a new portal container id="innercontent" added by the work turning the web content tool into a proper portlet and do away with one iframe (thanks Dr. Chuck). Notice the CSS definitions (float: left;width:100%)
>> 
>> This extra container is there to prevent specifically the float drop that you are reporting. 
>> 
>> So if you are going to use the portlet version of the web content you need the container (in trunk but not in  Sakai 2.9-SNAPSHOT you have), and properly styled in portal.css.
>> 
>> Is the portlet version of the web content slated for 2.9.2? Will need to update the documentation for this.
>> 
>> Thanks.
>> 
>>  - Gonzalo
>> 
>> <image.png>
>> 
>> 
>> On Mon, May 20, 2013 at 1:51 PM, Gonzalo Silverio <gsilver at umich.edu> wrote:
>> Mustansar,
>> 
>> Could I have guest access to a system that shows this? I will report back on what I find.
>> 
>> Thanks.
>> 
>>   - Gonzalo
>> 
>> 
>> On Mon, May 20, 2013 at 1:47 PM, Mustansar Mehmood <mustansar at rice.edu> wrote:
>> Hi,
>>      I have Sakai 2.9.x version of Web Content  tool, and perhaps due to skin modifications there is a huge space between title of the tool and the form for pointing to a website. I have attacched the screenshot. 
>> This may be because of skin changes I have made as QA servers for Sakai do not have this issue.  However at this point this is not telling where a certain change is propagating :(
>> I am hoping someone knows what aspect of neo-default skin may be changing it. 
>>  
>>  -- 
>> Mustansar Mehmood
>> Educational System Developer& Integrator
>> 
>> Information Technology  
>> 6100 Main St. MS 119
>> Houston Texas 77005
>> 
>> Phone:(713)348-2523
>> Fax  :(713)348 6099 
>> email:mustansar at rice.edu
>> 
>> 
>> 
>> 
>> 
>> I have yet to see any problem, however complicated, which, when,you  looked at it in the right way, did not become still more complicated. 
>>     -- Poul Anderson 
>> 
>> 
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>> 
>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>> 
>> 
>> 
>> -- 
>> - Gonzalo
>> 
>> 
>> 
>> -- 
>> - Gonzalo
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>> 
>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
> 
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> 
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130520/0b39896c/attachment.html